From: Tom Lane <tgl@sss.pgh.pa.us>
To: Karsten Hilbert <Karsten.Hilbert@gmx.net>
cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
        pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
In-reply-to: <20181103121419.GA3885@hermes.hilbert.loc>
References: <20181101152723.zq2dtcgntmcmr4br@alvherre.pgsql>
 <18072.1541087036@sss.pgh.pa.us> <20181101160007.GJ2954@hermes.hilbert.loc>
 <32192.1541217418@sss.pgh.pa.us> <20181103121419.GA3885@hermes.hilbert.loc>
Comments: In-reply-to Karsten Hilbert <Karsten.Hilbert@gmx.net>
	message dated "Sat, 03 Nov 2018 13:14:19 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <30593.1541259589.1@sss.pgh.pa.us>
Date: Sat, 03 Nov 2018 11:39:49 -0400
Message-ID: <30594.1541259589@sss.pgh.pa.us>
Precedence: bulk

Karsten Hilbert <Karsten.Hilbert@gmx.net> writes:
> On Fri, Nov 02, 2018 at 11:56:58PM -0400, Tom Lane wrote:
>> I was feeling baffled about this, but it suddenly occurs to me that maybe
>> the bug fixed in 040a1df61/372102b81 explains this.

> So, I guess I can work around the issue by the above
> manoeuvre and report back once 040a1df61/372102b81 is
> released.
> Anything else you'd want me to look into ?

Don't suppose you'd want to build a server with 372102b81 applied
and see if it works?

			regards, tom lane