| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Per-database and per-user GUC settings |
| Date: | 2002-02-01 17:40:05 |
| Message-ID: | Pine.LNX.4.30.0202011238280.687-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-02-01 17:44:47 | Re: Per-database and per-user GUC settings |
| Previous Message | Elaine Lindelef | 2002-02-01 17:37:58 | Re: timestamp weirdness |