Sync dev-16 branch with the latest changes #973
Merged
Conversation
This file contains 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
Member
hughcapet
commented
Feb 19, 2024
•
hughcapet
commented
- Change maintainer to team ACID
- Patroni 3.1.2 + Update Patroni to 3.2.2
- Return pod_ip param to k8s config in Patroni
- Add replay-lag function
- Add toggle to enable grouping log by date/instance in s3
- Remove redundant code
- No pg_partman update from <5.X during major upgrade
- Add function to monitor sequences
- Ensure correct bin_dir for pg params configuration
* Various tests fixes - Try both gnu and non-gnu 'date' command syntax - Cleanup all test containers - Fix scope name * Fix flaky tests: - wait backup before upgrade - drop table with OIDs in upgrade container Co-authored-by: Max Neverov <[email protected]> --------- Co-authored-by: Max Neverov <[email protected]>
* setup default image when cleaning up containers * update readme to run test * Add md extension to tests README --------- Co-authored-by: Polina Bungina <[email protected]>
* Patroni 3.1.0, timescaledb 2.11.2 * Align with the new Patroni code API
Co-authored-by: Sergey Dudoladov <[email protected]>
- wait_all_streaming/wait_zero_lag with configurable replica count - create table with oids using special func, not in the initial schema - add pg_repack extension to the initial schema - separate func for creating timescaledb objects - set WALE_BACKUP_THRESHOLD_PERCENTAGE to a higher value to ensure wal-e replica bootsrap method in test suite 5 - single verify_clone_upgrade func - adjust comments and formatting - ensure test suite 4 actually restores latest backup from PG10 and then upgrades
* add toggle to enable grouping log by date * add information in environment.rst * Update ENVIRONMENT.rst Co-authored-by: Polina Bungina <[email protected]> --------- Co-authored-by: Polina Bungina <[email protected]>
Due to the noticeable number of backward-incompatible changes in pg_parman 5.0, we better force users to prepare and check everything before actually upgrading the extension. So if performing major upgrade with pg_partman pre 5.X installed, we skip automatic update of it
Make in-place upgrade code use the bin_dir of the proper version throught the whole process, so that ConfigHandler.write_postgresql_conf() validates provided params using the proper PG version.
|
👍 |
1 similar comment
|
👍 |
Sign up for free
to join this conversation on GitHub.
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.