| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tyler Brock <tyler(dot)brock(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Segfault during queries |
| Date: | 2021-10-29 14:29:50 |
| Message-ID: | 627890.1635517790@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Tyler Brock <tyler(dot)brock(at)gmail(dot)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(at)postgres:[22200]:ERROR:
> cache lookup failed for type 0 2021-10-29 11:08:10
> UTC:172.23.17.171(54332):postgres(at)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tyler Brock | 2021-10-29 15:08:57 | Re: Segfault during queries |
| Previous Message | Scott Ribe | 2021-10-29 14:27:45 | Re: Segfault during queries |