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>
Subject: Re: backend crash on DELETE, reproducible locally
In-reply-to: <4kp.XAMr.3k5V4ORoB1t.1RtVIt@seznam.cz>
References: <20181101160007.GJ2954@hermes.hilbert.loc>
 <20181101152723.zq2dtcgntmcmr4br@alvherre.pgsql>
 <18072.1541087036@sss.pgh.pa.us> <32192.1541217418@sss.pgh.pa.us>
 <4kp.XAMr.3k5V4ORoB1t.1RtVIt@seznam.cz>
Comments: In-reply-to <obouda@email.cz>
	message dated "Sat, 03 Nov 2018 20:19:19 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <23467.1541273894.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Sat, 03 Nov 2018 15:38:14 -0400
Message-ID: <23468.1541273894@sss.pgh.pa.us>
Precedence: bulk

<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