| From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(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:45:09 |
| Message-ID: | 550DCA45.2080602@archidevsys.co.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22/03/15 08:34, Joshua D. Drake wrote:
>
> On 03/21/2015 12:00 AM, Mark Kirkwood wrote:
>
>>
>> -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!
>
> I don't agree with this at all. On the one hand:
>
> Postgres: So many settings people have no idea where to start (unless
> they have background)
>
> vs
>
> Postgres: Only the settings that are "needed" for 95% of installations.
>
> JD
>
>
How about 2 config files?
One marked adult^H^H^H^H^H power users only, or some such, with the
really dangerous or unusual options?
Cheers,
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2015-03-21 19:48:13 | Re: Remove fsync ON/OFF as a visible option? |
| Previous Message | Fabien COELHO | 2015-03-21 19:42:56 | Re: PATCH: pgbench - merging transaction logs |