Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Kapila <amit.kapila@huawei.com>
Cc: "'Stephen Frost'" <sfrost@snowman.net>,
"'Josh Berkus'" <josh@agliodbs.com>,
"'Andres Freund'" <andres@2ndquadrant.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
Date: 2013-08-05T12:18:33Z
Lists: pgsql-hackers
Amit Kapila <amit.kapila@huawei.com> writes: > On Monday, August 05, 2013 11:57 AM Tom Lane wrote: >> My point here is just that we should keep the parameter values in plain >> text files, > Here by text files, do you mean to say you are expecting > file-per-guc-setting? No, I don't think this argument really says much one way or the other about one-file vs one-file-per-GUC. I'm just lobbying against the "put them in a catalog" idea. regards, tom lane