From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: ERROR: relation "sql_features" does not exist |
Date: | 2021-04-26 17:10:47 |
Message-ID: | 2267860.1619457047@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> I tried to write a query that does lateral join between
> information_schema.tables and pgstattuple function.
> select * from information_schema.tables, lateral(select * from
> pgstattuple(table_name::name)) s where table_type = 'BASE TABLE';
> The query finished by strange error
> postgres=# select * from information_schema.tables, lateral(select * from
> pgstattuple(table_name::name)) s where table_type = 'BASE TABLE';
> ERROR: relation "sql_features" does not exist
> When I set search_path to information_schema, then the query is running.
> But there is not any reason why it should be necessary.
Nope, this is classic user error, nothing else. "table_name::name"
is entirely inadequate as a way to reference a table that isn't
visible in your search path. You have to incorporate the schema
name as well.
Ideally you'd just pass the table OID to the OID-accepting version of
pgstattuple(), but of course the information_schema schema views
don't expose OIDs. So basically you need something like
pgstattuple((quote_ident(table_schema)||'.'||quote_ident(table_name))::regclass)
although perhaps format() could help a little here.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2021-04-26 17:14:04 | Re: compute_query_id and pg_stat_statements |
Previous Message | Magnus Hagander | 2021-04-26 17:06:01 | Re: compute_query_id and pg_stat_statements |