From: Tom Lane <tgl@sss.pgh.pa.us>
To: jack <jack4pg@a7q.com>
cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: constant crashing
In-reply-to: <8GbSO-R5Ho1vhKDGY1znn08HJINRDYqFt_rBzSZ93n8sZTntsn61LvF4lCdPCZGF1SzahlFz03tZboOCXsCGPoBxqJe676QC-EIIF4HppzI=@a7q.com>
References: <8GbSO-R5Ho1vhKDGY1znn08HJINRDYqFt_rBzSZ93n8sZTntsn61LvF4lCdPCZGF1SzahlFz03tZboOCXsCGPoBxqJe676QC-EIIF4HppzI=@a7q.com>
Comments: In-reply-to jack <jack4pg@a7q.com>
	message dated "Sun, 14 Apr 2024 19:22:17 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <533978.1713123045.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 14 Apr 2024 15:30:45 -0400
Message-ID: <533979.1713123045@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/533979.1713123045%40sss.pgh.pa.us>
Precedence: bulk

jack <jack4pg@a7q.com> writes:
> Here is an excerpt of /var/log/postgresql/postgresql-16-main.log
> 2024-04-14 12:17:43.153 EDT [1227] LOG: server process (PID 7289) was te=
rminated by signal 11: Segmentation fault

That's pretty interesting; it suggests an actual PG bug.
Can you get a stack trace from that?  See

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_=
backend

Also, it's probably time you showed us the complete DDL definition
for the tables you're working with.  It's fairly hard to believe
this would happen without something rather out-of-the-ordinary
in the definitions.  Or ... do you have any PG extensions installed?

			regards, tom lane