<obouda@xxxxxxxx> 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
