From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Permanent settings |
Date: | 2008-02-19 16:11:27 |
Message-ID: | 47BAFFAF.1010004@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Aidan Van Dyk wrote:
>>> Any "set permanent" settings should be *appended* to the main config
>>> file, preferably with a comment line, like:
>>> # Set by user <USER> from client <CLIENT> on <TIMESTAMP>
>>> some_guc option = some_value
>>>
>> Are you suggesting we keep appending? So if I set the same parameter 100
>> times, it would show up on 100 rows?
>>
>
> In my opinion, absolutely. It's easy, safe, and the "overhead"
> associated with it is minimal, and not in any critical path "work" path.
> Add to that the fact that the admin can easily clean up the file any
> time he wants too.
>
>
I think this is quite unacceptable and ugly. Creating an ever-growing
file that the admin would have to clean up by hand is horrid.
ISTM that this whole area is likely to be difficult unless we move to a
more structured config file (JSON, anyone?)
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2008-02-19 16:14:59 | Re: Permanent settings |
Previous Message | Aidan Van Dyk | 2008-02-19 16:11:05 | Re: Permanent settings |