Horton

Re: backend crash on DELETE, reproducible locally

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ondřej Bouda <obouda@email.cz>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Ondřej Bouda <bouda@edookit.com>, pgsql-general@lists.postgresql.org, Karsten Hilbert <Karsten.Hilbert@gmx.net>
Date: 2018-11-06T19:49:44Z
Lists: pgsql-hackers, pgsql-general 
=?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda@email.cz> writes:
> I thought triggers should be suspected. However, even when all the three 
> triggers have been disabled (ALTER TABLE DISABLE TRIGGER), the UPDATE 
> crashed the server.

Foreign-key triggers too?

> What else could I try?

A stack trace would be really helpful.

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

			regards, tom lane

Commits

  1. Disable recheck_on_update optimization to avoid crashes.

  2. Allow HOT updates for some expression indexes