Re: backend crash on DELETE, reproducible locally
Karsten Hilbert <karsten.hilbert@gmx.net>
From: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, pgsql-general@lists.postgresql.org
Date: 2018-11-03T16:03:14Z
Lists: pgsql-hackers, pgsql-general
On Sat, Nov 03, 2018 at 11:39:49AM -0400, Tom Lane wrote: > 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? Yeah, I feared that answer ;-) However, I lack the skills and the machine(s) to do so ... I will, at any rate, report back when the existing fix is released. Karsten -- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
Commits
-
Disable recheck_on_update optimization to avoid crashes.
- 05f84605dbeb 11.1 landed
- 5d28c9bd73e2 12.0 landed
-
Allow HOT updates for some expression indexes
- c203d6cf81b4 11.0 cited