From: Tom Lane <tgl@sss.pgh.pa.us>
To: wobbet@wobbet.com, Robert Sanford <wobbet@gmail.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Segmentation Fault
In-reply-to: 
 <CABa+nRuatSjnqsPfnoo0APzgeM1Um94FesYj6H1YKB1qJ8JoqA@mail.gmail.com>
References: 
 <CABa+nRvwZy_5t1QF9NJNGwAf03tv_PO_Sg1FsN1+-3Odb1XgBA@mail.gmail.com>
 <CABa+nRuatSjnqsPfnoo0APzgeM1Um94FesYj6H1YKB1qJ8JoqA@mail.gmail.com>
Comments: In-reply-to Robert Sanford <wobbet@gmail.com>
	message dated "Wed, 13 Sep 2023 17:31:12 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3030991.1694649537.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 13 Sep 2023 19:58:57 -0400
Message-ID: <3030992.1694649537@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3030992.1694649537%40sss.pgh.pa.us>
Precedence: bulk

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