Re: postgres access violation in pg_detoast_datum - Mailing list pgsql-bugs

From Álvaro Herrera
Subject Re: postgres access violation in pg_detoast_datum
Date
Msg-id 202510210815.er7dclxccrak@alvherre.pgsql
Whole thread Raw
In response to postgres access violation in pg_detoast_datum  (Arnd Empting <arnd.empting@koerber.com>)
List pgsql-bugs
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"



pgsql-bugs by date:

Previous
From: Miroslav Pankov
Date:
Subject: TLS verification to intermediate trust anchor with psql
Next
From: Amit Langote
Date:
Subject: Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)