Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault

From: varun kamal <kamalvarun2004(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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 16:54:11
Message-ID: CAAy1k4zZMxY8xbEyp0NqWScsN-r52kZvrKQ5xeVvDDBVTU6EXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "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
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-05-13 18:11:01 Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
Previous Message Alvaro Herrera 2021-05-13 16:52:59 Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type