| From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fix for log_min_error_messages |
| Date: | 2003-01-29 02:32:52 |
| Message-ID: | Pine.LNX.4.21.0301291332020.20993-100000@linuxworld.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | eric@did-it.com | 2003-01-29 04:00:20 | Re: tsearch comments |
| Previous Message | Dave Cramer | 2003-01-29 02:02:05 | Re: Request for qualified column names |