| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "kamalvarun2004(at)gmail(dot)com" <kamalvarun2004(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault |
| Date: | 2021-05-13 15:41:24 |
| Message-ID: | 1518254.1620920484@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Thursday, May 13, 2021, PG Bug reporting form <noreply(at)postgresql(dot)org>
> wrote:
>> PostgreSQL version: 12.2
>> We are facing an issue once in 2 days that Postgres instance crashes with
>> following error
> You need to upgrade to a supported version (12.7 in your major version
> line).
Yeah, that would certainly be the first thing to try. If the problem is
still there, we'd really need quite a bit more information to diagnose
it. A stack trace from the point of the crash would be quite helpful:
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
Even better would be if you can reduce the problem to a self-contained
test case, though I realize that might be hard.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-05-13 15:45:00 | BUG #17008: pg_dump doesn't dump a sequence with bigint type |
| Previous Message | David G. Johnston | 2021-05-13 14:41:03 | Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault |