| From: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com> |
| Cc: | "Magnus Hagander" <magnus(at)hagander(dot)net>, "Csaba Nagy" <nagy(at)ecircle-ag(dot)com>, "Aidan Van Dyk" <aidan(at)highrise(dot)ca>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Permanent settings |
| Date: | 2008-02-19 17:37:30 |
| Message-ID: | 1A6E6D554222284AB25ABE3229A927627155DC@nrtexcus702.int.asurion.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> Gregory Stark wrote:
>
> > The alternative is to have two files and read them both. Then if you
> change a
> > variable which is overridden by the other source you can warn that
the
> change
> > is ineffective.
> >
> > I think on balance the include file method is so much simpler that I
> prefer it.
>
> I think this is a good idea. I would suggest being able to query
> exactly which config file a setting came from -- so you can see
whether
> it's the stock postgresql.conf, or the locally-modified
> postgresql.local.conf.
>
So a junior DBA goes to manage the db. Makes a change the
postgresql.conf file and bounces the db. The change doesn't stick.
That doesn't sound like fun and it also sounds like Oracle's spfile and
pfile.
Jon
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-19 17:50:16 | Re: Including PL/PgSQL by default |
| Previous Message | David Fetter | 2008-02-19 17:32:05 | Re: Including PL/PgSQL by default |