Skip site navigation (1) Skip section navigation (2)

Re: Server does not start when log_statement_stats is set to on

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 (view raw or flat)
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

In response to

Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2007-12-26 18:43:07
Subject: Re: Server does not start when log_statement_stats is setto on
Previous:From: Alvaro HerreraDate: 2007-12-26 17:50:24
Subject: Re: Server does not start when log_statement_stats is setto on

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group