Re: Fix premature xmin advancement during fast forward decoding

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, shveta malik <shveta(dot)malik(at)gmail(dot)com>
Subject: Re: Fix premature xmin advancement during fast forward decoding
Date: 2025-04-28 09:20:02
Message-ID: CAA4eK1+TBP5y-dEz6o388e5Fjo4wS4JD2XXsDRev82kzgg6ABA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 27, 2025 at 12:33 PM Zhijie Hou (Fujitsu)
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
>
> I also adjusted the commit message to mention the commit f49a80c4
> as suggested by Amit.
>

Pushed.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2025-04-28 09:33:05 Re: Fix slot synchronization with two_phase decoding enabled
Previous Message Nazir Bilal Yavuz 2025-04-28 09:12:50 Re: Add pg_buffercache_mark_dirty[_all] functions to the pg_buffercache