On 07/08/2014 08:18 PM, Amit Kapila wrote: >> Yes, but even well behaved users will see this type of error, because > initdb uncomments certain values (ones that are dead certs for being > changed via ALTER SYSTEM subsequently like shared_buffers), and then - > bang! your next reload gets that "your postgresql.conf contains errors" > message. > > That is the reason, why I have suggested up-thread that uncommented > values should go to postgresql.auto.conf, that will avoid any such > observations for a well-behaved user
Not an effective solution for three reasons: 1) Some users will copy over their older pg.conf's to 9.4, which will already have shared_buffers uncommented; 2) Some distros ship their own pg.conf; 3) Doesn't solve the issue of overlapping files in conf.d, which is the same problem. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
