From: Álvaro Herrera <alvherre@kurilemu.de>
To: Arnd Empting <arnd.empting@koerber.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: postgres access violation in pg_detoast_datum
Date: Tue, 21 Oct 2025 11:21:24 +0300
Message-ID: <202510210815.er7dclxccrak@alvherre.pgsql> (raw)
In-Reply-To: <AS8PR04MB773582904779B1E30D3CF0C388F2A@AS8PR04MB7735.eurprd04.prod.outlook.com>
On 2025-Oct-21, Arnd Empting wrote:
> Crashing postgres executable due to access violation in pg_detoast_datum
>
> ExceptionAddress: 00007ff6ef1e86f0 (postgres!pg_detoast_datum)
> ExceptionCode: c0000005 (Access violation)
You may well have corrupt data in your tables. I suspect some parts of
the detoasting code are still not robust enough against that and could
cause server crashes.
It would be good, at some point, to look into fuzzing the toast code
with random bytes so that we can report errors rather than crashing ...
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Uno puede defenderse de los ataques; contra los elogios se esta indefenso"
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: alvherre@kurilemu.de, arnd.empting@koerber.com, pgsql-bugs@lists.postgresql.org
Subject: Re: postgres access violation in pg_detoast_datum
In-Reply-To: <202510210815.er7dclxccrak@alvherre.pgsql>
* 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