From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tyler Brock <tyler.brock@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: Segfault during queries
In-reply-to: 
 <CACr_h8TsU0Swpa=0OcXUbHx69BNBeyYJf6B-q-sdEkTYY7rHPg@mail.gmail.com>
References: 
 <CACr_h8TsU0Swpa=0OcXUbHx69BNBeyYJf6B-q-sdEkTYY7rHPg@mail.gmail.com>
Comments: In-reply-to Tyler Brock <tyler.brock@gmail.com>
	message dated "Fri, 29 Oct 2021 14:05:46 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <627889.1635517790.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Oct 2021 10:29:50 -0400
Message-ID: <627890.1635517790@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/627890.1635517790%40sss.pgh.pa.us>
Precedence: bulk

Tyler Brock <tyler.brock@gmail.com> writes:
> Is there anything I can do to prevent this or anything i can look at to =
try
> and diagnose what is happening here? I=E2=80=99m running Postgres 12.7 a=
nd cannot
> tell if this is a symptom of a bug or just misconfiguration.

> What I see in the error logs is:

> 2021-10-29 11:08:10 UTC:172.23.17.171(54332):postgres@postgres:[22200]:E=
RROR:
> cache lookup failed for type 0 2021-10-29 11:08:10
> UTC:172.23.17.171(54332):postgres@postgres:[22200]:STATEMENT: COPY (SELE=
CT
> ROW_TO_JSON(t) FROM (=E2=80=A6 the query above...) TO STDOUT 2021-10-29 =
11:08:10
> UTC::@:[19406]:LOG: server process (PID 22200) was terminated by signal =
11:
> Segmentation fault

That's most certainly a bug.  Can you get a stack trace from the crash?

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

			regards, tom lane