| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
| Date: | 2013-01-26 15:52:51 |
| Message-ID: | 1359215571.76036.YahooMailNeo@web162904.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> More people seem to have voted for the single file approach but I still
>> haven't understood why...
>
> Me neither. Having an include directory seems good, but I can't think
> why we'd want to clutter it up with a bajillion automatically
> generated files. One .auto file that gets overwritten at need seems
> way nicer.
The single-value per file approach punts the concurrency issues and
ordering issues to the OS, which might significantly simplify the
patch. I'm not sure that the niceness of the all-in-one-file
approach justifies the extra code. If you ever want to view them
all in one file as of some moment in time, there is always:
cat * | less
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | james | 2013-01-26 16:04:35 | Re: Strange Windows problem, lock_timeout test request |
| Previous Message | Andrew Dunstan | 2013-01-26 15:27:04 | Re: json api WIP patch |