public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: jack <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: constant crashing
Date: Sun, 14 Apr 2024 15:30:45 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <8GbSO-R5Ho1vhKDGY1znn08HJINRDYqFt_rBzSZ93n8sZTntsn61LvF4lCdPCZGF1SzahlFz03tZboOCXsCGPoBxqJe676QC-EIIF4HppzI=@a7q.com>
References: <8GbSO-R5Ho1vhKDGY1znn08HJINRDYqFt_rBzSZ93n8sZTntsn61LvF4lCdPCZGF1SzahlFz03tZboOCXsCGPoBxqJe676QC-EIIF4HppzI=@a7q.com>

jack <[email protected]> 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 terminated 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

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: constant crashing
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox