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

Hi,

I am not sure what you mean, I am not a developer.

What I did:

started gdb and then:

(gdb) set pagination 0
(gdb) attach 84465
Attaching to process 84465

0x00007f58bd33143e in __libc_read (fd=0, buf=0x7ffe09e53c80, nbytes=1)
at ../sysdeps/unix/sysv/linux/read.c:27
27      ../sysdeps/unix/sysv/linux/read.c: No such file or directory.
(gdb) continue
Continuing.
[Inferior 1 (process 84465) exited normally]
(gdb) backtrace full
No stack.
(gdb) quit

that's it.

I think I have to get a stacktrace of the postgres server process , not
of psql but I do not how to do that.

Herwig

On 22/04/2021 12:52, Michael Paquier wrote:
> On Thu, Apr 22, 2021 at 12:09:44PM +0200, Herwig Goemans wrote:
>> Anyway, with the trigger in place we encounter PG server crashes.
>>
>> I am having trouble collection a trace file because when I attach gdb to the
>> process:
>>
>> 0x00007f99b46f7a07 in epoll_wait (epfd=5, events=0x561321b40630,
>> maxevents=maxevents(at)entry=1, timeout=timeout(at)entry=-1) at
>> ../sysdeps/unix/sysv/linux/epoll_wait.c:30
>> 30      ../sysdeps/unix/sysv/linux/epoll_wait.c: No such file or directory.
>> (gdb) quit
> What does a simple "bt" print?
> --
> Michael