From: Michael Paquier <michael@paquier.xyz>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: rootcause000@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
Date: Wed, 4 Oct 2023 16:24:45 +0900
Message-ID: <ZR0TPQvVQqIzuPsG@paquier.xyz> (raw)
In-Reply-To: <9fc4118d2a8f2290d8598a9c4d451c4c90b17cee.camel@cybertec.at>
References: <18146-04e908c662113ad5@postgresql.org>
<9fc4118d2a8f2290d8598a9c4d451c4c90b17cee.camel@cybertec.at>
On Wed, Oct 04, 2023 at 09:17:11AM +0200, Laurenz Albe wrote:
> Data corruption like this is not necessarily caused by a PostgreSQL bug.
Err, well... A failure on the end-of-vacuum truncation should not
lead to corruption afterwards as well, and this ought to be safe even
if this step failed. This is a very tricky problem that nobody has
really looked into yet.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (832B, ../ZR0TPQvVQqIzuPsG@paquier.xyz/2-signature.asc)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: michael@paquier.xyz, laurenz.albe@cybertec.at, rootcause000@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
In-Reply-To: <ZR0TPQvVQqIzuPsG@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox