From: Tom Lane <tgl@sss.pgh.pa.us>
To: Karsten Hilbert <Karsten.Hilbert@gmx.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
Date: Sat, 03 Nov 2018 11:39:49 -0400
Message-ID: <30594.1541259589@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, Karsten.Hilbert@gmx.net, alvherre@2ndquadrant.com, pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
In-Reply-To: <30594.1541259589@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox