Re: BUG #17229: Segmentation Fault after upgrading to version 13

From: "Efrain J(dot) Berdecia" <ejberdecia(at)yahoo(dot)com>
To: "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17229: Segmentation Fault after upgrading to version 13
Date: 2021-10-18 12:54:29
Message-ID: 161365152.4123667.1634561669073@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Trying to attach it again...
core.28085.sig11.zip

|
|
| |
core.28085.sig11.zip

|

|

|

Efrain J. Berdecia

On Monday, October 18, 2021, 08:48:45 AM EDT, Efrain J. Berdecia <ejberdecia(at)yahoo(dot)com> wrote:

Here's the core dump.
Please let me know if there's anything we can provide to troubleshoot this situation.
Efrain J. Berdecia

On Wednesday, October 13, 2021, 04:53:04 PM EDT, Efrain J. Berdecia <ejberdecia(at)yahoo(dot)com> wrote:

This a production server but I'll check with out server admin group.

Sent from Yahoo Mail on Android

On Wed, Oct 13, 2021 at 3:55 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Ever since we upgraded to PostgreSQL version 13 we are sporadically getting
> segmentation faults for the following process and all existing connections
> get killed and our streaming replication process goes down.

Hmm, can you get a stack trace from the crash?  See

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

            regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Borodin 2021-10-18 13:23:05 Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Previous Message Efrain J. Berdecia 2021-10-18 12:48:45 Re: BUG #17229: Segmentation Fault after upgrading to version 13