Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Amit Kapila <amit.kapila@huawei.com>, 'Greg Stark' <stark@mit.edu>,
'Alvaro Herrera' <alvherre@2ndquadrant.com>,
'Fujii Masao' <masao.fujii@gmail.com>,
'Robert Haas' <robertmhaas@gmail.com>,
'Dimitri Fontaine' <dimitri@2ndquadrant.fr>,
pgsql-hackers@postgresql.org, 'Josh Berkus' <josh@agliodbs.com>,
'Tom Lane' <tgl@sss.pgh.pa.us>
Date: 2013-08-02T13:45:05Z
Lists: pgsql-hackers
On 2013-08-02 08:41:09 -0400, Stephen Frost wrote: > Perhaps having the file be a heap file instead of anything a sysadmin > can be asked to go hack would also make it more clear that this is an > internal PG file which is to be managed only through PG and stop all > this arguing about how "oh, they can just fix it by twiddling things in > $PGDATA" is considered by some to be an acceptable solution. Heck, it'd > also keep the number of files down while allowing more fine-grained > modifications and writes (iow, we wouldn't have to rewrite the whole > file every time..). Crash recovery & PGC_SIGHUP|PGC_POSTMASTER… Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services