From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
Date: Sat, 3 Nov 2018 15:06:02 -0500
Message-ID: <ff3b1482-55f5-48c7-26b9-8006b4524221@gmail.com> (raw)
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>
On 11/03/2018 02:19 PM, obouda@email.cz wrote:
> Hello,
>
> 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.
>
> I would like to ask, however: could the same problemarise from an UPDATE
> statement (also on a table with an AFTER trigger), or would that be
> another bug (technical details below)?
> As the bug causes our production servers segfault several times a day,
> we'd like to solve the problem as soon as possible. Do I understand it
> correctly that if we dump and restore the database, the bug should not
> occur (until the next ALTER TABLE ADD COLUMN - which we'll avoid until the
> patch is released)?
You can dump that single table, truncate the table (presuming no FKs) and
then restore it.
--
Angular momentum makes the world go 'round.
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: ronljohnsonjr@gmail.com, pgsql-general@lists.postgresql.org
Subject: Re: backend crash on DELETE, reproducible locally
In-Reply-To: <ff3b1482-55f5-48c7-26b9-8006b4524221@gmail.com>
* 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