Re: BUG #16976: server crash when deleting via a trigger on a foreign table - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #16976: server crash when deleting via a trigger on a foreign table
Date
Msg-id CA+hUKG+XCzNWV82tjgVTUtQ09M6Fuxuow+jCKryPhg+QSo1D_w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16976: server crash when deleting via a trigger on a foreign table  (Herwig Goemans <herwig.goemans@gmail.com>)
Responses Re: BUG #16976: server crash when deleting via a trigger on a foreign table  (Herwig Goemans <herwig.goemans@gmail.com>)
List pgsql-bugs
On Thu, Apr 22, 2021 at 10:09 PM Herwig Goemans
<herwig.goemans@gmail.com> wrote:
> And I cannot execute anything in the attached (psql) process,

A couple of notes about the attach-then-crash approach:  It should be
"postgres", not "psql", that you attach to, and then you need to type
"cont" to tell the debugger to allow execution to continue, or it'll
just block as you described. Sometimes it will stop execution when
signals arrive, and you can disable that with eg "handle SIGUSR1
nostop" and then go back to executing with "cont" again.  Once you
make it crash, you'll be able to use "bt" to see exactly where, but as
mentioned it'll just be a bunch of big hex numbers unless the symbols
are installed; at the least it'll show which modules (postgres,
informix_fdw.so or such).



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: posgres 12 bug (partitioned table)
Next
From: PG Bug reporting form
Date:
Subject: BUG #16978: Nested CTEs give ERROR in v13