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

From Michael Paquier
Subject Re: [PATCH] Renumber confusing value for GUC_UNIT_BYTE
Date
Msg-id YxbobofjLkY8r+EQ@paquier.xyz
Whole thread Raw
In response to Re: [PATCH] Renumber confusing value for GUC_UNIT_BYTE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Renumber confusing value for GUC_UNIT_BYTE
List pgsql-hackers
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.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Ibrar Ahmed
Date:
Subject: Re: Allow pageinspect's bt_page_stats function to return a set of rows instead of a single row
Next
From: Ibrar Ahmed
Date:
Subject: Re: Proposal to provide the facility to set binary format output for specific OID's per session