Add options to pg_upgrade #125
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long since we need to have binary upgrade tests in our CI. One example is the timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement th `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a sucessful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement th `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a sucessful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement th `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement th `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
@fabriziomello Thank you for the contrib |
It will be added in the next testgres version 1.10.1 |
Thank you @demonolock |
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 24, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to fabriziomello/timescaledb that referenced this pull request May 25, 2024
It's long we need to have binary upgrade tests in our CI. One example is timescale#6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes timescale#3868 timescale#4428
fabriziomello added a commit to timescale/timescaledb that referenced this pull request May 26, 2024
It's long we need to have binary upgrade tests in our CI. One example is #6935 (and others) that can be prevented if we have such kind of test in our CI. To implement the `pg_upgrade` test we used the python Testing Framework for PostgreSQL (https://.com/postgrespro/testgres). Unfortunately the testing framework don't have the ability to retain the pg_upgrade log files after a successful execution, then we created a PR to make it possible and we'll use this ed version until we get the code merged and released on upstream. postgrespro/testgres#125 Closes #3868 #4428
Sign up for free to join this conversation on . Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
No description provided.