Re: Fix for log_min_error_messages - Mailing list pgsql-hackers

From Gavin Sherry
Subject Re: Fix for log_min_error_messages
Date
Msg-id Pine.LNX.4.21.0301291332020.20993-100000@linuxworld.com.au
Whole thread Raw
In response to Re: Fix for log_min_error_messages  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Tue, 28 Jan 2003, Bruce Momjian wrote:

> Peter Eisentraut wrote:
> > Bruce Momjian writes:
> > 
> > > Due to my error, log_min_error messages went into 7.3.X with the wrong
> > > default, and the wrong listed options.
> > >
> > > This fixes the bug in CVS current and 7.3.X.  Patch attached.
> > 
> > Why does "panic" mean "off"?  If you set it to "panic" don't you still get
> > the "panic" messages?  I'm sure the implementation makes sense, but the
> > way it's documented seems confusing.
> 
> Yep, it is really weird.  Gavin didn't want to have separate routines to
> validate the various flags, so all the "level" messages can take all the
> possible values, and there is no 'off' so "panic" seems the best.
> only meaningful ones.

I offered, from memory, three different possible solutions. setting it to
PANIC seemed the most popular.

Gavin



pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Request for qualified column names
Next
From: "John Liu"
Date:
Subject: poor performance of subquery in psql