Re: Fix for consume_xids advancing XIDs incorrectly - Mailing list pgsql-hackers

From Kirill Reshke
Subject Re: Fix for consume_xids advancing XIDs incorrectly
Date
Msg-id CALdSSPix0UFXTHwxWUXPJkjXJt9diGG6jwJNBSPxk5_5Ai4yEw@mail.gmail.com
Whole thread Raw
In response to Re: Fix for consume_xids advancing XIDs incorrectly  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Wed, 30 Oct 2024 at 12:01, Yushi Ogiwara
<btogiwarayuushi@oss.nttdata.com> wrote:
>
> I made a new patch (skip_xid_correctly.diff) that incorporates the
> points we discussed:
>
> 1. Fix the issue that consume_xids consumes nxids+1 XIDs.
> 2. Update lastxid when calling GetTopFullTransactionId() to support
> nxids==1 case.
> 3. Forbid consume_xids when nxids==0.
> 4. Add comments explaining the return values of consume_xids and
> consume_xids_until, and the rationale for incrementing consumed++ when
> GetTopFullTransactionId() is called.
>
> Also, I made another patch (support_blksz_32k.diff) that supports the
> block size == 32K case.
>
> Best,
> Yushi Ogiwara
>


Hi!

There is review comments that need to be addressed in [1]
Patch status now is waiting on author

[1] https://www.postgresql.org/message-id/CAD21AoCthHcSQ5zeeivNpiz7HMi_FPG-dtwDDNYUx2oKG36bCQ%40mail.gmail.com

-- 
Best regards,
Kirill Reshke



pgsql-hackers by date:

Previous
From: Kirill Reshke
Date:
Subject: Re: Sequence Access Methods, round two
Next
From: a.mitrokhin@postgrespro.ru
Date:
Subject: Building an extension in a separate directory from the source files.