Re: Fix premature xmin advancement during fast forward decoding - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Fix premature xmin advancement during fast forward decoding
Date
Msg-id CAD21AoA1sQN8OY7O_Z8hLeGxY-Bdafe8B4+0JD6W4C+EpMFhvg@mail.gmail.com
Whole thread Raw
In response to Re: Fix premature xmin advancement during fast forward decoding  (Amit Kapila <amit.kapila16@gmail.com>)
Responses RE: Fix premature xmin advancement during fast forward decoding
List pgsql-hackers
On Sat, Apr 26, 2025 at 5:01 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Sat, Apr 26, 2025 at 12:01 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> >
> > On Fri, Apr 25, 2025 at 4:42 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> > >
> > > Can you think of any better ideas?
> >
> > No idea. Hmm, there seems no reasonable way to fix this issue for back
> > branches. I consented to the view that these costs were something that
> > we should have paid from the beginning.
> >
>
> Right, I feel we should go with the simple change proposed by Hou-San
> for now to fix the bug. If, in the future, we encounter any cases
> where such optimizations can help for fast-forward mode, then we can
> consider it. Does that sound reasonable to you?

Yes, agreed with this approach.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Get rid of integer divide in FAST_PATH_REL_GROUP() macro
Next
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Fix premature xmin advancement during fast forward decoding