| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| startup_scripts.patch | no | |||||
| acceptance_tests_system_patroni.patch | =================================================================== | no | ||||
| requirements_setuptools.patch | =================================================================== | no | ||||
| offline_intersphinx.patch | =================================================================== | no | ||||
| requirements_cdiff.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 | ||||
| python3.6-testsuite-fix.patch | no | |||||
| disable_sphinx_github_style.patch | no | |||||
| sphinx_autodoc_fix.patch | no |