Re: BUG #18258: The redo of the drop db wal needs to forward the Min Recovery Point

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: azurezhao8369(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Noah Misch <noah(at)leadboat(dot)com>
Subject: Re: BUG #18258: The redo of the drop db wal needs to forward the Min Recovery Point
Date: 2026-11-15 03:41:45
Message-ID: CAGRkXqSpTPX8uDRSv04xbYuuZFHZeTvT+7GT7qMYJf=dX9CDwA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Michael,

> Did you do a search of the mailing
> lists regarding that?

Thanks for looking. Yes, I searched. The closest is a 2009 review [1]
where Heikki said an XLogFlush() in dbase_redo() did not help, because
his concern was the window after the commit record.

That became the ForceSyncCommit() flush in xact_redo_commit(), so
the window between the drop record and its commit was never covered.

Thanks,
Shihao

[1] https://postgr.es/m/4B1B8824.2070808@enterprisedb.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message shihao zhong 2026-11-15 03:51:12 Re: BUG #19702: decode() accepts Base64 payload after terminal padding
Previous Message shihao zhong 2026-11-15 03:33:17 Re: bug: Gather rescan keeps the first scan's tuple bound in workers