Re: Per-database and per-user GUC settings

Bruce Momjian wrote:
> > > 1. postgresql.conf contains a setting for some variable, say
> > > sort_mem=1000. DBA starts postmaster with a command-line option to
> > > override the variable, say --sort_mem=2000. Works fine, until he
> > > SIGHUPs the postmaster for some unrelated reason, at which point
> > > sort_mem snaps back to 1000.
> >
> > This sort of thing was once considered a feature, until someone came along
> > and overloaded SIGHUP for unreleated things. ;-)
>
> I agree we should not propagate config changes to children on SIGHUP.
> The only major question I had was that command-line flags get wiped out
> by postgresql.conf settings on SIGHUP. I know someone pointed this
> out but has a solution been proposed? That would surprise any admin.

Added to TODO:

* Prevent SIGHUP and 'pg_ctl reload' from changing command line
specified parameters to postgresql.conf defaults

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026