| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)CommandPrompt(dot)com> |
| Cc: | Devrim GÜNDÜZ <devrim(at)CommandPrompt(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Server does not start when log_statement_stats is set to on |
| Date: | 2007-12-26 18:35:36 |
| Message-ID: | 10202.1198694136@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)CommandPrompt(dot)com> writes:
> Tom Lane wrote:
>> There are a bunch of other GUC assign hooks that behave similarly.
>> Perhaps it'd be sensible to emit these complaints as LOG messages
>> when we're dealing with a noninteractive source (ie, the config file)?
> I was wondering whether we could make this error message (and
> equivalent ones) be the FATAL one that prevents the server from
> starting.
There is some good reason, which I don't recall at the moment, why
assign-hooks (and most of the rest of GUC) shouldn't FATAL in the
middle of processing a config file. However a LOG seems relatively
harmless, and better than not emitting anything.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-12-26 18:43:07 | Re: Server does not start when log_statement_stats is set to on |
| Previous Message | Alvaro Herrera | 2007-12-26 17:50:24 | Re: Server does not start when log_statement_stats is set to on |