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+hUKGLdmvPzEWN_yfAqOPpFDYNXWjiPNTjX2buSHRvW0urnTg@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 Wed, Jan 8, 2025 at 4:22 PM Michael Paquier <michael@paquier.xyz> wrote:
> It seems to me that you meant to do the following in the back
> branches:

> -       return smgrtruncate2(reln, forknum, nforks, old_nblocks, nblocks);
> +       smgrtruncate2(reln, forknum, nforks, old_nblocks, nblocks);

Right, that was accepted by my compiler and apparently almost all the
others, but is not really allowed in C (it's allowed in C++, and
useful for generic forwarding).  Duh.  Will fix.



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Incorrect result in certain expressions of anti-join
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_rewind fails on Windows where tablespaces are used