From: Tom Lane <tgl@sss.pgh.pa.us>
To: phoedos16@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16833: postgresql 13.1 process crash every hour
In-reply-to: <16833-12d1cd7c13c78bde@postgresql.org>
References: <16833-12d1cd7c13c78bde@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 22 Jan 2021 05:37:56 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1154091.1611329011.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Jan 2021 10:23:31 -0500
Message-ID: <1154092.1611329011@sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Process crash inside docker containter 2-3 times per hour without any
> additional information
> ./postgresql-Thu-00.log:2021-01-21 00:11:34 UTC [1]: user=3D,db=3D,app=3D=
,client=3D
> LOG:  server process (PID 20071) was terminated by signal 11: Segmentati=
on
> fault

Hm, please see if you can get a stack trace:

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_=
backend

Also try to figure out what query(s) are causing the crash.
(It's unlikely that the postmaster log doesn't provide more
information than you've shared here.)

> I can share postgresql.conf, process crash core dumps for analysis

Core dumps are unlikely to help anyone else; they are too
machine-specific.  Not to mention that they might contain
sensitive data.  You'll need to examine them yourself.

			regards, tom lane