Re: [PATCH] Stop ALTER SYSTEM from making bad assumptions
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Ian Barwick <ian.barwick@2ndquadrant.com>
Cc: Stephen Frost <sfrost@snowman.net>, Amit Kapila <amit.kapila16@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2019-06-21T14:45:02Z
Lists: pgsql-hackers
On Mon, Jun 17, 2019 at 10:50 AM Ian Barwick <ian.barwick@2ndquadrant.com> wrote: > In Pg12, the code in pg_basebackup implies the correct thing to do is append to .auto.conf, > but as demonstrated that can cause problems with duplicate entries. Yeah. To me, forcing every tools author to use postgresql.conf parsing tools rather than just appending to the file is a needless burden on tool authors. I'd vote for just having ALTER SYSTEM silently drop all but the last of duplicated entries. It sounds like I might be in the minority, but I feel like the reactions which suggest that this is somehow heresy are highly overdone. Given that the very first time somebody wanted to do something like this in core, they picked this approach, I think we can assume that it is a natural approach which other people will also attempt. There doesn't seem to be any good reason for it not to Just Work. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Doc: improve documentation about postgresql.auto.conf.
- e3ddb112f245 10.11 landed
- 7f77f2aec3d0 11.6 landed
- 57980bdf62f4 9.4.25 landed
- 45aaaa42fefa 13.0 landed
- 372d6a8918e0 12.0 landed
- 1ab92aaa97ce 9.5.20 landed
- 0969a7aa3240 9.6.16 landed
-
Fix ALTER SYSTEM to cope with duplicate entries in postgresql.auto.conf.
- f1bf619acdff 13.0 landed
- f8c9a08520ee 10.11 landed
- a4b0d955bd23 9.4.25 landed
- 75b2f011f642 12.0 landed
- 4784ad7a370e 9.6.16 landed
- 32d38f54a369 11.6 landed
- 29f9b1819a72 9.5.20 landed