Re: Per-database and per-user GUC settings - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Per-database and per-user GUC settings
Date
Msg-id Pine.LNX.4.30.0202011238280.687-100000@peter.localdomain
Whole thread Raw
In response to Re: Per-database and per-user GUC settings  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Per-database and per-user GUC settings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Bruce Momjian writes:

> 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.

I think it's desirable and fully intentional.  How else would you override
command-line args without restarting the server?  I can see where there
might be a concern, but in my mind, if you're using command-line arguments
in permanent setups, you're not trying hard enough.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Per-database and per-user GUC settings
Next
From: "Zeugswetter Andreas SB SD"
Date:
Subject: [PATCHES] FAQ_AIX patch for 7.2