Re: Remove fsync ON/OFF as a visible option?

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, 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>, 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-22 01:41:17
Message-ID: 86zj75x0zm.fsf@jerry.enova.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:

> On 03/21/2015 12:45 PM, Gavin Flower wrote:
>
>>>
>> 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?
>>
>
> That has come up before in many threads. I don't know that we need to
> go down that path again. Consider, power users don't need a separate
> config. They can create their own or use alter system.
>

10 years ago I was already feeling like postgresql.conf was unwieldy
and have on many occasions stripped them down only to live lines without
any comments whatsoever.

In fact I'd argue that due to how verbose the file is presently as
shipped, it makes it that much more likely that someone looking at is
isn't going to notice something as alarming as fsync=off :-)

> 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"

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2015-03-22 01:41:44 Re: PATCH: numeric timestamp in log_line_prefix
Previous Message Bruce Momjian 2015-03-22 01:35:02 Re: PATCH: numeric timestamp in log_line_prefix