ERROR,XX000,"cache lookup failed for type 0"

Поиск
Список
Период
Сортировка
От tao jin
Тема ERROR,XX000,"cache lookup failed for type 0"
Дата
Msg-id BYAPR06MB504767EEB45B5A2A71031F8FAA2B0@BYAPR06MB5047.namprd06.prod.outlook.com
обсуждение исходный текст
Список pgsql-bugs
hi ,

I had met a segment fault problem in PostgreSQL 12.1.And it happened 
randomly,I could not use the query to repeat the segment fault.

     PostgreSQL 12.1 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 7.3.1 
20180303 (Red Hat 7.3.1-5), 64-bit

  Connection logged as below:

2019-12-26 07:26:56.133 
CST,,,187480,"172.17.12.216:38272",5e03f040.2dc58,1,"",2019-12-26 
07:26:56 CST,,0,LOG,00000,"connection received: host=172.17.12.216 
port=38272",,,,,,,,"BackendInitialize, postmaster.c:4296",""
2019-12-26 07:26:56.134 
CST,"logdev","dpos1",187480,"172.17.12.216:38272",5e03f040.2dc58,2,"authentication",2019-12-26 
07:26:56 CST,4/59649,0,LOG,00000,"connection authorized: user=logdev 
database=dpos1",,,,,,,,"PerformAuthentication, postinit.c:303",""
2019-12-26 07:26:56.283 
CST,"logdev","dpos1",187480,"172.17.12.216:38272",5e03f040.2dc58,3,"SELECT",2019-12-26 
07:26:56 CST,4/59654,0,ERROR,XX000,"cache lookup failed for type 0",,,,,,"
       WITH pg_source AS (SELECT 
""public"".""dpos_pmp_activityexposure_prod"".* FROM 
""public"".""dpos_pmp_activityexposure_prod""  WHERE 
""public"".""dpos_pmp_activityexposure_prod"".""sale_id"" LIKE 
'%01d93294-bf06-412e-b09b-fa6c3ee56168%'::unknown   ) SELECT null AS 
total_result_set, pg_catalog.count(_postgrest_t) AS page_total, 
array[]::text[] AS header, coalesce(json_agg(_postgrest_t), 
'[]')::character varying AS body
       FROM ( SELECT * FROM pg_source) _postgrest_t 
",,"getBaseTypeAndTypmod, lsyscache.c:2328","app - 172.17.12.216:41240

The query was generated by  postgrest(version 5.2.0).

WITH pg_source AS (
   SELECT
     public.dpos_pmp_activityexposure_prod.*
   FROM
     public.dpos_pmp_activityexposure_prod
   WHERE
     public.dpos_pmp_activityexposure_prod.sale_id LIKE 
'%01d93294-bf06-412e-b09b-fa6c3ee56168%' :: unknown
)
SELECT
   null AS total_result_set,
   pg_catalog.count(_postgrest_t) AS page_total,
   array[] :: text[] AS header,
   coalesce(
     json_agg(_postgrest_t),
     '[]'
   ):: character varying AS body
FROM
   (
     SELECT
       *
     FROM
       pg_source
   ) _postgrest_t

The backtrace in core dump file was:

gdb -q -c core.102993 /usr/local/pgsql-12/bin/postgres
Reading symbols from /usr/local/pgsql-12/bin/postgres...(no debugging 
symbols found)...done.
[New LWP 102993]
Core was generated by `postgres: logdev dpos1 172.17.12.216(59568) S'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000000000490688 in FreeTupleDesc ()
(gdb) bt
#0  0x0000000000490688 in FreeTupleDesc ()
#1  0x0000000000872c68 in ResourceOwnerRememberCatCacheListRef ()
#2  0x00000000009c3280 in __func__.10906 ()
#3  0x0000000002507520 in ?? ()
#4  0x00000001024e4f80 in ?? ()
#5  0x0000000002518b48 in ?? ()
#6  0x0000000000000000 in ?? ()



В списке pgsql-bugs по дате отправления:

Предыдущее
От: Dam
Дата:
Сообщение: Re:Re: BUG #16179: is it reasonable to callbackpgss_post_parse_analyze or pg_hint_plan_post_parse_analyze ???
Следующее
От: Amit Langote
Дата:
Сообщение: Re: A row-level trigger on a partitioned table is not created on asub-partition created later