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
Date: Fri, 29 Oct 2021 10:29:50 -0400
Message-ID: <627890.1635517790@sss.pgh.pa.us> (raw)
In-Reply-To: <CACr_h8TsU0Swpa=0OcXUbHx69BNBeyYJf6B-q-sdEkTYY7rHPg@mail.gmail.com>
References: <CACr_h8TsU0Swpa=0OcXUbHx69BNBeyYJf6B-q-sdEkTYY7rHPg@mail.gmail.com>
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’m running Postgres 12.7 and 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]:ERROR:
> cache lookup failed for type 0 2021-10-29 11:08:10
> UTC:172.23.17.171(54332):postgres@postgres:[22200]:STATEMENT: COPY (SELECT
> ROW_TO_JSON(t) FROM (… 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, tyler.brock@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Segfault during queries
In-Reply-To: <627890.1635517790@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox