| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Arnd Empting <arnd(dot)empting(at)koerber(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: postgres access violation in pg_detoast_datum |
| Date: | 2025-10-21 08:21:24 |
| Message-ID: | 202510210815.er7dclxccrak@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2025-10-21 09:11:51 | Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift) |
| Previous Message | Miroslav Pankov | 2025-10-21 08:15:29 | TLS verification to intermediate trust anchor with psql |