| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parsing config files in a directory |
| Date: | 2009-10-26 14:45:33 |
| Message-ID: | 28713.1256568333@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane escribi:
>> Personally I think this is just a matter of usage. If you want to use
>> SET PERSISTENT, don't set values manually in postgresql.conf.
> I agree, except that some things are defined in postgresql.conf by
> initdb and you probably want to be able to change them by SET PERSISTENT
> anyway (e.g. lc_messages, listen_addresses, shared_buffers)
Well, initdb would also find it a lot easier to dump its settings into a
machine-generated file. I don't think we have to continue doing things
exactly the same way there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-10-26 14:47:57 | Re: Parsing config files in a directory |
| Previous Message | Robert Haas | 2009-10-26 14:44:38 | Re: Endgame for all those SELECT FOR UPDATE changes: fix plan node order |