From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | vik(at)postgresfriends(dot)org |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Subject: | Re: BUG #17723: cache lookup failed for type 0 |
Date: | 2022-12-16 17:10:56 |
Message-ID: | 3697954.1671210656@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> This query:
> WITH RECURSIVE
> run(x, y) AS (
> SELECT 0, 0
> UNION ALL
> SELECT x, y FROM run AS r WHERE r.is_cycle
> )
> CYCLE x, y SET is_cycle USING path
> TABLE run
> ;
> in which I mistakenly tried to access the is_cycle column from inside the
> wle, provokes the following error:
> ERROR: XX000: cache lookup failed for type 0
> LOCATION: typeOrDomainTypeRelid, parse_type.c:699
Yeah. We are calling addRangeTableEntryForCTE inside parse analysis of
the CTE's query, and it's generating a ParseNamespaceItem with p_vartype = 0
because analyzeCTE hasn't yet identified the cycle_mark_type. That
eventually results in a Var with vartype 0, confusing later parse analysis.
It looks to me like we can just move that part of the code up to before
we recurse to parse_sub_analyze, though. AFAICS, identification of the
cycle column type needn't (and had better not) depend on any
characteristics of the CTE's query.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2022-12-16 17:52:29 | BUG #17724: All autovacuum workers operate on 1 db at a time |
Previous Message | Tom Lane | 2022-12-16 16:12:17 | Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...' |