It's long since we need to have binary upgrade tests in our CI. Oneexample is thetimescale#6935 (and others) that can be prevented if we have suchkind of test in our CI.To implement th `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a sucessful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement th `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a sucessful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement th `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement th `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleistimescale#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closestimescale#3868timescale#4428

It's long we need to have binary upgrade tests in our CI. One exampleis#6935 (and others) that can be prevented if we have such kind oftest in our CI.To implement the `pg_upgrade` test we used the python Testing Frameworkfor PostgreSQL (https://github.com/postgrespro/testgres).Unfortunately the testing framework don't have the ability to retain thepg_upgrade log files after a successful execution, then we created a PRto make it possible and we'll use this patched version until we get thecode merged and released on upstream.postgrespro/testgres#125Closes#3868#4428