Postgres Pro
Downloads
Home   >   mailing lists

Re: Segmentation Fault - Mailing list pgsql-bugs

From Robert Sanford
Subject Re: Segmentation Fault
Date
Msg-id CABa+nRs0x9DR52xyRa2COJOad-9VfjYQkDRcJOPACGsSCN_QJQ@mail.gmail.com
Whole thread Raw
In response to Re: Segmentation Fault  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Segmentation Fault
List pgsql-bugs
Tree view
Woke up this morning excited to create a core dump and... it worked.

Not only does it work, it works fast. Query time dropped from 5.5s to 1.2s. That was what I was hoping to get out of the VACUUM ANALYZE.

Very confused. I don't get it. I hope it doesn't happen again, but if it does I'll get the core dump. 

rjsjr


On Wed, Sep 13, 2023 at 6:58 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Robert Sanford <wobbet@gmail.com> writes:
> I realized that when I was running GDB I just took a snap of when it
> failed. Here I've added after continuing and requesting a backtrace.

This is still quite unhelpful; it appears to show normal behavior in
a process that's not the failing one.  There is some advice about
collecting useful backtraces at

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

I'd counsel the method of enabling core dumps and then attaching
gdb to a core file, rather than dealing with live processes.

                        regards, tom lane

pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #18108: server process was terminated by signal 11: Segmentation fault
Next
From: Stephen Flavin
Date:
Subject: Re: BUG #18109: enable_partitionwise_aggregate does not apply when inserting or updating