From: Tom Lane <tgl@sss.pgh.pa.us>
To: vik@postgresfriends.org
Cc: pgsql-bugs@lists.postgresql.org, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: BUG #17723: cache lookup failed for type 0
Date: Fri, 16 Dec 2022 12:10:56 -0500
Message-ID: <3697954.1671210656@sss.pgh.pa.us> (raw)
In-Reply-To: <17723-2c4985ff111e7bba@postgresql.org>
References: <17723-2c4985ff111e7bba@postgresql.org>
PG Bug reporting form <noreply@postgresql.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
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, vik@postgresfriends.org, peter.eisentraut@enterprisedb.com
Subject: Re: BUG #17723: cache lookup failed for type 0
In-Reply-To: <3697954.1671210656@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