| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | jack <jack4pg(at)a7q(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: constant crashing |
| Date: | 2024-04-14 19:30:45 |
| Message-ID: | 533979.1713123045@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
jack <jack4pg(at)a7q(dot)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 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jack | 2024-04-14 19:44:40 | re: constant crashing |
| Previous Message | Vijaykumar Jain | 2024-04-14 19:25:06 | Re: constant crashing |