Re: backend crash on DELETE, reproducible locally
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: obouda@email.cz
Cc: "Alvaro Herrera" <alvherre@2ndquadrant.com>,
pgsql-general@lists.postgresql.org,
"Karsten Hilbert" <Karsten.Hilbert@gmx.net>
Date: 2018-11-03T19:38:14Z
Lists: pgsql-hackers, pgsql-general
<obouda@email.cz> writes: > we reached the exactly same problem after upgrading to PostgreSQL 11 - the > server crashed on a DELETE statement with a trigger. We also observed an > AFTER DELETE trigger receiving NULL values in OLD. Now I see the problem > seems to be solved (theoretically). Unfortunately, we are not able to build > the server with the patch, so we cannot confirm that. However, when we just > copied the database (within the same server), the same DELETE executed on > the copy with no problems. Yeah, dump/reload would make the problem go away. > I would like to ask, however: could the same problem arise from an UPDATE > statement (also on a table with an AFTER trigger), or would that be another > bug (technical details below)? Same bug. regards, tom lane
Commits
-
Disable recheck_on_update optimization to avoid crashes.
- 05f84605dbeb 11.1 landed
- 5d28c9bd73e2 12.0 landed
-
Allow HOT updates for some expression indexes
- c203d6cf81b4 11.0 cited