From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Alexander Lakhin <exclusion@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17064: Parallel VACUUM operations cause the error "global/pg_filenode.map contains incorrect checksum"
Date: Tue, 22 Jun 2021 20:41:19 -0400
Message-ID: <1944432.1624408879@sss.pgh.pa.us> (raw)
In-Reply-To: <YNKBazxEayjtyb1x@paquier.xyz>
References: <17064-bb0d7904ef72add3@postgresql.org>
<ac119d1e-05d1-f050-b92a-0a524d68b848@iki.fi>
<CA+hUKGJ98=MOjDCnMAC5gSpkzrrey=O+aEQJ1OY03C=cVtiwkA@mail.gmail.com>
<1715251.1624371066@sss.pgh.pa.us>
<YNKBazxEayjtyb1x@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> On Tue, Jun 22, 2021 at 10:11:06AM -0400, Tom Lane wrote:
>> Shouldn't we instead file a kernel bug report? I seem to recall that
>> POSIX guarantees atomicity of these things up to some operation size.
>> Or is that just for pipe I/O?
> Even if this is recognized as a bug report, it seems to me that we'd
> better cope with an extra lock for instances that may run into this
> issue anyway in the future, no? Just to be on the safe side.
Based on the evidence at hand, we can't really say whether the writes
are non-atomic. If that's the case then we have much worse problems
than just needing to add a lock. Thus, I think we need to get some
kernel people involved.
regards, tom lane
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: tgl@sss.pgh.pa.us, michael@paquier.xyz, thomas.munro@gmail.com, hlinnaka@iki.fi, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17064: Parallel VACUUM operations cause the error "global/pg_filenode.map contains incorrect checksum"
In-Reply-To: <1944432.1624408879@sss.pgh.pa.us>
* 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