From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Remove fsync ON/OFF as a visible option? |
Date: | 2015-03-21 19:31:38 |
Message-ID: | 550DC71A.7050007@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 03/20/2015 04:09 PM, Robert Haas wrote:
> Thus far, the rule for postgresql.conf has been that pretty much
> everything goes in there, and that's a defensible position. Other
> reasonable options would be to ship the file with a small handful of
> settings in it and leave everything else, or to ship it completely
> empty of comments with only those settings that initdb sets and
> nothing else. I'd be OK a coherent policy change in this area, but
> just removing one or two setting seems like it will be confusing
> rather than helpful.
I would agree with this. I imagine there is only about a dozen, dozen
and a half that need to be there by default.
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, @cmdpromptinc
Now I get it: your service is designed for a customer
base that grew up with Facebook, watches Japanese seizure
robot anime, and has the attention span of a gnat.
I'm not that user., "Tyler Riddle"
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2015-03-21 19:32:08 | Re: Remove fsync ON/OFF as a visible option? |
Previous Message | Jaime Casanova | 2015-03-21 19:14:30 | Re: Remove fsync ON/OFF as a visible option? |