Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
Robert Haas <robertmhaas@gmail.com>,
Dimitri Fontaine <dimitri@2ndquadrant.fr>,
Andres Freund <andres@2ndquadrant.com>,
Josh Berkus <josh@agliodbs.com>, Tom Lane <tgl@sss.pgh.pa.us>,
Fujii Masao <masao.fujii@gmail.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2013-08-20T02:57:28Z
Lists: pgsql-hackers
* Amit Kapila (amit.kapila16@gmail.com) wrote: > If both are okay, then I would like to go with second option (include > file mechanism). > I think by default, we should allow auto file to be included and if > user faces any problem or otherwise, > then he can decide to disable it. If it's enabled by default, then we need to ship an 'auto' file which is empty by default... I don't particularly like that (implies that an empty file is acceptable and not an error condition, which it otherwise probably would be...). I'm still not a big fan of enabling it by default tho. Thanks, Stephen