From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas@vondra.me>
Cc: Bram van der Vos <bram.van.der.vos@axisinto.nl>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: file corruption goes undetected
Date: Thu, 06 Aug 2026 18:09:17 -0400
Message-ID: <1460711.1786054157@sss.pgh.pa.us> (raw)
In-Reply-To: <9abdddef-4c08-4d47-8879-9265e164dacb@vondra.me>
References: <943a83bf-78d1-4231-a9de-c24740e09d7a@axisinto.nl>
<9abdddef-4c08-4d47-8879-9265e164dacb@vondra.me>
Tomas Vondra <tomas@vondra.me> writes:
> This is expected behavior, not a bug. It'd be great to detect these
> kinds of data corruption, but data checksums can't do that (and we don't
> have other protections).
I suspect what's really happening in this example is that the query
result is produced entirely from pages in shared buffers, so we don't
notice that the underlying disk files have been clobbered. We would
notice once we have occasion to actually read the junk data.
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, tomas@vondra.me, bram.van.der.vos@axisinto.nl, pgsql-bugs@lists.postgresql.org
Subject: Re: file corruption goes undetected
In-Reply-To: <1460711.1786054157@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