From: Herwig Goemans <herwig.goemans@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-bugs@lists.postgresql.org, PG Bug reporting form <noreply@postgresql.org>
Subject: Re: BUG #16976: server crash when deleting via a trigger on a foreign table
Date: Wed, 21 Apr 2021 16:08:16 +0200
Message-ID: <45a2dc04-54a8-690d-a959-47e791a7f686@gmail.com> (raw)
In-Reply-To: <756273.1619012414@sss.pgh.pa.us>
References: <16976-abe0cb88252bc02e@postgresql.org>
<756273.1619012414@sss.pgh.pa.us>
Hi,
I was in the process of reproducing the problem and following the
guidelines to produce the stack trace... but now it works.
I asked my colleagues if they changed anything and will let you know.
Thanks for the quick response, and I will keep you posted if I have any
news.
Kind regards,
Herwig
On 21/04/2021 15:40, Tom Lane wrote:
>> I have experienced a server crash when deleting from a table that ahs a
>> before trigger on it. The before trigger calls a function that deletes from
>> a foreign (informix) table.
> Hm, can you get a stack trace from that?
>
> https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
>
> It seems fairly likely that the bug is in whatever FDW you're using
> rather than in core Postgres. A stack trace would help to
> confirm or refute that.
>
> 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-bugs@postgresql.org
Cc: herwig.goemans@gmail.com, tgl@sss.pgh.pa.us, noreply@postgresql.org
Subject: Re: BUG #16976: server crash when deleting via a trigger on a foreign table
In-Reply-To: <45a2dc04-54a8-690d-a959-47e791a7f686@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