Re: [PATCH] Renumber confusing value for GUC_UNIT_BYTE - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Renumber confusing value for GUC_UNIT_BYTE
Date
Msg-id 316575e0-64b8-3db6-865c-165b94958ce0@enterprisedb.com
Whole thread Raw
In response to Re: [PATCH] Renumber confusing value for GUC_UNIT_BYTE  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 06.09.22 08:27, Michael Paquier wrote:
> On Tue, Sep 06, 2022 at 01:57:53AM -0400, Tom Lane wrote:
>> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>>> I think renumbering this makes sense.  We could just leave the comment
>>> as is if we don't come up with a better wording.
>>
>> +1, I see no need to change the comment.  We just need to establish
>> the precedent that values within the GUC_UNIT_MEMORY field can be
>> chosen sequentially.
> 
> +1.

committed without the comment change



pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: Patch to address creation of PgStat* contexts with null parent context
Next
From: Christoph Berg
Date:
Subject: Re: [postgis-devel] PostGIS and json_categorize_type (Re: pgsql: Revert SQL/JSON features)