Re: backend crash on DELETE, reproducible locally

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: backend crash on DELETE, reproducible locally
Date: 2018-11-03 15:39:49
Message-ID: 30594.1541259589@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jerry Sievers 2018-11-03 16:02:08 Re: Logical replication hangs up.
Previous Message Karsten Hilbert 2018-11-03 12:14:19 Re: backend crash on DELETE, reproducible locally

Browse pgsql-hackers by date

  From Date Subject
Next Message Karsten Hilbert 2018-11-03 16:03:14 Re: backend crash on DELETE, reproducible locally
Previous Message Phil Florent 2018-11-03 13:43:33 RE: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian