| 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:48:45 |
| Message-ID: | 1750477103.4124637.1634561325552@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Efrain J. Berdecia | 2021-10-18 12:54:29 | Re: BUG #17229: Segmentation Fault after upgrading to version 13 |
| Previous Message | PG Bug reporting form | 2021-10-18 11:20:14 | BUG #17236: Postgres core on pstate->p_multiassign_exprs |