| From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remove fsync ON/OFF as a visible option? |
| Date: | 2015-03-21 19:14:30 |
| Message-ID: | CAJKUy5iA08H3+5eAbfH88utHZE5q=X3jwDCk-s-Z9FmW33CJ6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
El mar 21, 2015 2:00 AM, "Mark Kirkwood" <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
escribió:
>
> On 21/03/15 19:28, Jaime Casanova wrote:
>>
>> what about not removing it but not showing it in postgresql.conf? as a
>> side note, i wonder why trace_sort is not in postgresql.conf...
>> other option is to make it a compile setting, that why if you want to
>> have it you need to compile and postgres' developers do that routinely
>> anyway
>>
>
> -1
>
> Personally I'm against hiding *any* settings. Choosing sensible defaults
- yes! Hiding them - that reeks of secret squirrel nonsense and overpaid
Oracle dbas that knew the undocumented settings for various capabilities. I
think/hope that no open source project will try to emulate that meme!
>
That ship has already sailed.
http://www.postgresql.org/docs/9.4/static/runtime-config-developer.html
--
Jaime Casanova
2ndQuadrant Consultant
Your PostgreSQL partner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2015-03-21 19:31:38 | Re: Remove fsync ON/OFF as a visible option? |
| Previous Message | Thom Brown | 2015-03-21 18:30:09 | Re: assessing parallel-safety |