On Fri, Jun 24, 2022 at 11:42:29AM +0100, Simon Riggs wrote: > This patch would undo a very important change - to keep servers > available by default and go back to the old behavior for a huge fleet > of Postgres databases. The old behavior of shutdown-on-change caused > catastrophe many times for users and in one case brought down a rather > large and important service provider, whose CTO explained to me quite > clearly how stupid he thought that old behavior was. So I will not > easily agree to allowing it to be put back into PostgreSQL, simply to > avoid adding a small amount of easy code into an orchestration layer > that could and should implement documented best practice. > > I am otherwise very appreciative of your insightful contributions, > just not this specific one.
Given this feedback, I intend to mark the associated commitfest entry as Withdrawn at the conclusion of the current commitfest. > Happy to discuss how we might introduce new parameters/behavior to > reduce the list of parameters that need to be kept in lock-step. Me, too. I don't have anything concrete to propose at the moment. I thought Horiguchi-san's idea of automatically running ALTER SYSTEM was intriguing, but I have not explored that in depth. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
