From: Tom Lane <tgl@sss.pgh.pa.us>
To: herwig.goemans@gmail.com, 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
In-reply-to: <16976-abe0cb88252bc02e@postgresql.org>
References: <16976-abe0cb88252bc02e@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Wed, 21 Apr 2021 12:39:30 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <756272.1619012414.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Apr 2021 09:40:14 -0400
Message-ID: <756273.1619012414@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/756273.1619012414%40sss.pgh.pa.us>
Precedence: bulk

> 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 f=
rom
> 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