Re: Change xl_hash_vacuum_one_page.ntuples from int to uint16

From: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Change xl_hash_vacuum_one_page.ntuples from int to uint16
Date: 2023-02-16 15:09:45
Message-ID: 399607d1-6aee-0715-0482-67e669b9d2a6@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2/16/23 1:26 PM, Drouvot, Bertrand wrote:
> Hi,
>
> On 2/16/23 12:00 PM, Amit Kapila wrote:
>> I think this would require XLOG_PAGE_MAGIC as it changes the WAL record.
>>
>
> Oh, I Was not aware about it, thanks! Will do in V2 (and in the logical
> decoding on standby patch as it adds the new field mentioned above).
>
>> BTW, how about a commit message like:
>> Change xl_hash_vacuum_one_page.ntuples from int to uint16.
>>
>> This will create two bytes of padding space in xl_hash_vacuum_one_page
>> which can be used for future patches. This makes the datatype of
>> xl_hash_vacuum_one_page.ntuples same as gistxlogDelete.ntodelete which
>> is advisable as both are used for the same purpose.
>>
>
> LGTM, will add it to V2!
>
Please find V2 attached.
The commit message also mention the XLOG_PAGE_MAGIC bump.

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

Attachment Content-Type Size
v2-0001-Change-xl_hash_vacuum_one_page.ntuples-from-int-t.patch text/plain 1.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2023-02-16 15:50:30 Re: logical decoding and replication of sequences, take 2
Previous Message Jonathan S. Katz 2023-02-16 15:06:37 Re: Move defaults toward ICU in 16?