Re: Defaults for GUC variables (was Re: pg_ctl reports
| От | Michael Brusser |
|---|---|
| Тема | Re: Defaults for GUC variables (was Re: pg_ctl reports |
| Дата | |
| Msg-id | DEEIJKLFNJGBEMBLBAHCKEIJDNAA.michael@synchronicity.com обсуждение исходный текст |
| Ответ на | Defaults for GUC variables (was Re: pg_ctl reports succes when start fails) (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
> Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes: > > Shouldn't it revert to the default value? > > No, not unless you think the postmaster should react to comments in the > postgresql.conf file, which is rather against my idea of a comment. > > However, you're not the first to get burnt by this mis-assumption, > so maybe we should do something about it. > > The low-tech solution to this would be to stop listing the default > values as commented-out entries, but just make them ordinary uncommented > entries. That way people who think "undoing my edit will revert the > change" would be right. > > Or we could try to make it actually work the way you seem to be > expecting. The only implementation I can think of is to reset GUC > variables to defaults just before scanning the .conf file ... ------ I have to say we never had any problems or misconception with how it currently works, but if this has to be changed I'd rather vote for the low-tech solution. Mike.
В списке pgsql-hackers по дате отправления: