Re: Remove redundant extra_desc info for enum GUC variables? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Remove redundant extra_desc info for enum GUC variables?
Date
Msg-id 28891.1211988004@sss.pgh.pa.us
Whole thread Raw
In response to Re: Remove redundant extra_desc info for enum GUC variables?  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Remove redundant extra_desc info for enum GUC variables?
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> Tom Lane wrote:
>> Yeah: LOG level sorts differently in the two cases; it's fairly high
>> priority for server log output and much lower for client output.

> Ok, easy fix if we break them apart. Should we continue to accept
> values that we're not going to care about, or should I change that at
> the same time? (for example, client_min_messages doesn't use INFO,
> but we do accept that in <= 8.3 anyway)

I'd be inclined to keep the actual behavior the same as it was.
We didn't document INFO for this variable, perhaps, but it's accepted
and has a well-defined behavior.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add dblink function to check if a named connection exists
Next
From: Gregory Stark
Date:
Subject: Re: Avoiding second heap scan in VACUUM