From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ondřej Bouda <obouda@email.cz>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Ondřej Bouda <bouda@edookit.com>
Cc: pgsql-general@lists.postgresql.org, Karsten Hilbert <Karsten.Hilbert@gmx.net>
Subject: Re: backend crash on DELETE, reproducible locally
Date: Tue, 06 Nov 2018 14:49:44 -0500
Message-ID: <31911.1541533784@sss.pgh.pa.us> (raw)
In-Reply-To: <8e260d7c-13e8-b398-14dd-2e079ff7e833@email.cz>
References: <20181106185255.776mstcyehnc63ty@alvherre.pgsql>
<8e260d7c-13e8-b398-14dd-2e079ff7e833@email.cz>
=?UTF-8?Q?Ond=c5=99ej_Bouda?= <obouda@email.cz> writes:
> I thought triggers should be suspected. However, even when all the three
> triggers have been disabled (ALTER TABLE DISABLE TRIGGER), the UPDATE
> crashed the server.
Foreign-key triggers too?
> What else could I try?
A stack trace would be really helpful.
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
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, obouda@email.cz, alvherre@2ndquadrant.com, bouda@edookit.com, Karsten.Hilbert@gmx.net
Subject: Re: backend crash on DELETE, reproducible locally
In-Reply-To: <31911.1541533784@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