Re: BUG #16976: server crash when deleting via a trigger on a foreign table

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Herwig Goemans <herwig(dot)goemans(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, PG Bug reporting form <noreply(at)postgresql(dot)org>
Subject: Re: BUG #16976: server crash when deleting via a trigger on a foreign table
Date: 2021-04-22 22:45:30
Message-ID: CA+hUKG+XCzNWV82tjgVTUtQ09M6Fuxuow+jCKryPhg+QSo1D_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Apr 22, 2021 at 10:09 PM Herwig Goemans
<herwig(dot)goemans(at)gmail(dot)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).

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-04-23 00:13:41 BUG #16978: Nested CTEs give ERROR in v13
Previous Message Tom Lane 2021-04-22 20:28:36 Re: posgres 12 bug (partitioned table)