From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Ondřej Bouda <bouda@edookit.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@lists.postgresql.org, Karsten Hilbert <Karsten.Hilbert@gmx.net>
Subject: Re: backend crash on DELETE, reproducible locally
Date: Tue, 6 Nov 2018 15:52:55 -0300
Message-ID: <20181106185255.776mstcyehnc63ty@alvherre.pgsql> (raw)
In-Reply-To: <d1823964-157d-34f5-f359-79da00872861@edookit.com>
On 2018-Nov-06, Ondřej Bouda wrote:
> So we dumped and restored all our databases. After that, the crash on DELETE
> never occurred (before, it was several times a day). However, the crash on
> UPDATE still occurs on specific rows. We are quite certain no ALTER TABLE
> statement was executed on the table after the restore.
> There are two AFTER INSERT OR UPDATE constraint triggers and one BEFORE
> INSERT OR UPDATE trigger on the table, all of which are implemented in
> plpgsql. Multiple physical servers, on separate databases with identical
> schema, crash on the same type of UPDATE query (different just in concrete
> values to be updated). The same code worked perfectly on 10.x.
>
> See the attached backtrace below. Can we do something else to catch the bug?
> Or can we hope for this bug to be already fixed and released in the upcoming
> version?
Hmm, this one smells like c203d6cf81b4 -- haven't seen any fixes for
that one. Can you share more details on this? I think the failing
update is on table with oid=557732818, but I might be wrong.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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: alvherre@2ndquadrant.com, bouda@edookit.com, tgl@sss.pgh.pa.us, Karsten.Hilbert@gmx.net
Subject: Re: backend crash on DELETE, reproducible locally
In-Reply-To: <20181106185255.776mstcyehnc63ty@alvherre.pgsql>
* 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