Re: Proposed GUC Variable - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Proposed GUC Variable
Date
Msg-id 15459.1030668148@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposed GUC Variable  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: Proposed GUC Variable  (Gavin Sherry <swm@linuxworld.com.au>)
List pgsql-hackers
Gavin Sherry <swm@linuxworld.com.au> writes:
> That's a pretty good idea. Now, what format will the argument take: text
> (NOTICE, ERROR, DEBUG, etc) or integer? The increasing severity is clear
> with numbers but the correlation to NOTICE, ERROR etc is undocumented
> IIRC. On the other hand, the textual form is clear but INFO < NOTICE <
> WARNING < ERROR < FATAL, etc, is note necessarily obvious.

The variable should take the same values as SERVER_MIN_MESSAGES and
impose the same priority order as it does.  I would assume you could
share code, or at worst copy-and-paste a few dozen lines.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Proposed GUC Variable
Next
From: Bruce Momjian
Date:
Subject: Re: tweaking MemSet() performance