Re: Per-database and per-user GUC settings
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Per-database and per-user GUC settings |
| Дата | |
| Msg-id | Pine.LNX.4.30.0202011238280.687-100000@peter.localdomain обсуждение исходный текст |
| Ответ на | Re: Per-database and per-user GUC settings (Bruce Momjian <pgman@candle.pha.pa.us>) |
| Ответы |
Re: Per-database and per-user GUC settings
|
| Список | 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 по дате отправления: