Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
Date
Msg-id CA+hUKG+CNA-LQ10=PGuk7MsduK+wT1NNtSg7=dAX4ir=wpPmNA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
On Thu, Feb 6, 2025 at 5:36 AM Andres Freund <andres@anarazel.de> wrote:
> On 2025-01-08 10:57:20 +1300, Thomas Munro wrote:
> > On Tue, Dec 24, 2024 at 6:51 PM Michael Paquier <michael@paquier.xyz> wrote:
> > > That's not really critical, so leaving them as they are is equally OK
> > > for me.  Looks good to me, otherwise.
> >
> > Thanks.  I pushed it just like that.
>
> I assume there's nothing left to do for the CF entry?
>
> https://commitfest.postgresql.org/51/5242/
>
> It doesn't matter that much anymore, with things not getting moved to new CFs,
> but probably still worth updating.

Done.



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #18796: Npgsql Driver: Foreign Key Read Inversion in INSERT Operations
Next
From: Chris BSomething
Date:
Subject: Re: Bug in psql