Debian Patches
Status for patroni/4.0.5-1
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| startup_scripts.patch | no | |||||
| acceptance_tests_system_patroni.patch | =================================================================== | no | ||||
| offline_intersphinx.patch | =================================================================== | no | ||||
| avoid_overwriting_configuration_during_boostrap.patch | commit a3776e0dfb2f0c5a9e5174f948122b8fb33ceebc Make backup copies of configuration files in config_dir. Before, the .backup files were always done in the data directory. However, if there is a distinct configuration directory, it seems logical to put them there. If config_dir is not configured, it defaults back to the data directory, so this will not change things for setups where postgresql.conf is in the data directory. On the other hand, it will help with setups where postgresql.conf is outside the data directory and has local changes. In this case, those no longer get overwritten on boostrap/clone from the primary's backup configuration file that is streamed to the boostrapped node. Close #2370 =================================================================== |
Michael Banck <michael.banck@credativ.de> | no | 2022-07-29 | ||
| regression_tests_skip_citus_test.patch | =================================================================== | no | ||||
| disable_sphinx_github_style.patch | =================================================================== | no | ||||
| replslot-cluster-type-attribute.patch | [PATCH] Add optional 'cluster_type' attribute to permanent replication slots. (#3229) This allows to set whether a particular permanent replication slot should always be created ('cluster_type=any', the default), or just on a primary ('cluster_type=primary') or standby ('cluster_type=standby') cluster, respectively. |
Michael Banck <michael.banck@credativ.de> | no | 2024-12-10 | ||
| reproducible_docs.patch | =================================================================== | no | ||||
| fix_conffile_perms.patch | [PATCH] Fix permissions of out-of-PGDATA created postgresql.conf. (#3308) Since 01d07f86c, the permissions of postgresql.conf created in PGDATA was explicitly set. However, the umask of the Patroni process was adjusted as well and as a result of this, Patroni would write postgresql.conf with 600 permissions if the configuration files are outside PGDATA. Fix this by using the original umask as mode for files created outside PGDATA. |
Michael Banck <michael.banck@credativ.de> | no | 2025-03-14 |