| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:48:41 |
| Message-ID: | 20091026144841.GG8812@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane escribió:
> 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.
Hmm, so it would create a "00initdb.conf" file instead of the current
mess with search & replace on the template? That sounds good.
(But to me this also says that SET PERSISTENT has to go over
00initdb.conf and add a comment mark to the setting.)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-10-26 14:51:48 | Re: Parsing config files in a directory |
| Previous Message | Tom Lane | 2009-10-26 14:47:57 | Re: Parsing config files in a directory |