Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault - Mailing list pgsql-bugs

From varun kamal
Subject Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault
Date
Msg-id CAAy1k4z6zBMMTTWNUP89UCpKWJxo_EsPCrBFGdm_9Q0+0q22kQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault  (varun kamal <kamalvarun2004@gmail.com>)
List pgsql-bugs
Dear Tom and David,

Kindly help me to understand below points.

1. Is it known bug in this particular version (12.2).
2. Upgrading to 12.7 will resolve this issue.

Regards,
Varun

On Thu, May 13, 2021, 10:24 PM varun kamal <kamalvarun2004@gmail.com> wrote:
Many thanks Tom and David.

We will try to upgrade to supported version. 

Regards,
Varun

On Thu, May 13, 2021, 9:11 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Thursday, May 13, 2021, PG Bug reporting form <noreply@postgresql.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

pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Segmentation fault when calling BlessTupleDesc in a C function in parallel on PostgreSQL-(12.6, 12.7, 13.2, 13.3)
Next
From: Eugen Konkov
Date:
Subject: Re: BUG #16968: Planner does not recognize optimization