Date: Wed, 13 Oct 2021 20:53:03 +0000 (UTC)
From: "Efrain J. Berdecia" <ejberdecia@yahoo.com>
Reply-To: "Efrain J. Berdecia" <ejberdecia@yahoo.com>
To: tgl@sss.pgh.pa.us
Cc: pgsql-bugs@lists.postgresql.org
Message-ID: <982785865.2767625.1634158383999@mail.yahoo.com>
In-Reply-To: <666112.1634154922@sss.pgh.pa.us>
References: <17229-bc836b4d1d2633bf@postgresql.org>
 <666112.1634154922@sss.pgh.pa.us>
Subject: Re: BUG #17229: Segmentation Fault after upgrading to version 13
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2767624_994115634.1634158383998"
Content-Length: 2846
Archived-At: 
 <https://www.postgresql.org/message-id/982785865.2767625.1634158383999%40mail.yahoo.com>
Precedence: bulk

------=_Part_2767624_994115634.1634158383998
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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

Sent from Yahoo Mail on Android=20
=20
  On Wed, Oct 13, 2021 at 3:55 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:   PG =
Bug reporting form <noreply@postgresql.org> writes:
> Ever since we upgraded to PostgreSQL version 13 we are sporadically getti=
ng
> segmentation faults for the following process and all existing connection=
s
> get killed and our streaming replication process goes down.

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

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_b=
ackend

=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0 regards, tom lane
 =20

------=_Part_2767624_994115634.1634158383998
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

This a production server but I'll check with out server admin group.<br id=
=3D"yMail_cursorElementTracker_1634158348336"><br><div id=3D"ymail_android_=
signature"><a id=3D"ymail_android_signature_link" href=3D"https://go.onelin=
k.me/107872968?pid=3DInProduct&amp;c=3DGlobal_Internal_YGrowth_AndroidEmail=
Sig__AndroidUsers&amp;af_wl=3Dym&amp;af_sub1=3DInternal&amp;af_sub2=3DGloba=
l_YGrowth&amp;af_sub3=3DEmailSignature">Sent from Yahoo Mail on Android</a>=
</div> <br> <blockquote style=3D"margin: 0 0 20px 0;"> <div style=3D"font-f=
amily:Roboto, sans-serif; color:#6D00F6;"> <div>On Wed, Oct 13, 2021 at 3:5=
5 PM, Tom Lane</div><div>&lt;tgl@sss.pgh.pa.us&gt; wrote:</div> </div> <div=
 style=3D"padding: 10px 0 0 20px; margin: 10px 0 0 0; border-left: 1px soli=
d #6D00F6;"> PG Bug reporting form &lt;<a shape=3D"rect" ymailto=3D"mailto:=
noreply@postgresql.org" href=3D"mailto:noreply@postgresql.org">noreply@post=
gresql.org</a>&gt; writes:<div class=3D"yqt1816356552" id=3D"yqtfd18038"><b=
r clear=3D"none">&gt; Ever since we upgraded to PostgreSQL version 13 we ar=
e sporadically getting<br clear=3D"none">&gt; segmentation faults for the f=
ollowing process and all existing connections<br clear=3D"none">&gt; get ki=
lled and our streaming replication process goes down.</div><br clear=3D"non=
e"><br clear=3D"none">Hmm, can you get a stack trace from the crash?&nbsp; =
See<br clear=3D"none"><br clear=3D"none"><a shape=3D"rect" href=3D"https://=
wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend" =
target=3D"_blank">https://wiki.postgresql.org/wiki/Generating_a_stack_trace=
_of_a_PostgreSQL_backend</a><br clear=3D"none"><br clear=3D"none">&nbsp;&nb=
sp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; regards, tom lane<div class=
=3D"yqt1816356552" id=3D"yqtfd23229"><br clear=3D"none"></div> </div> </blo=
ckquote>
------=_Part_2767624_994115634.1634158383998--