| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ExecRTCheckPerms() and many prunable partitions (sqlsmith) |
| Date: | 2023-02-12 23:37:11 |
| Message-ID: | 20230212233711.GA1316@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 29, 2022 at 10:37:56PM +0900, Amit Langote wrote:
> 0002 contains changes that has to do with changing how we access
> checkAsUser in some foreign table planning/execution code sites.
> Thought it might be better to describe it separately too.
This was committed as 599b33b94:
Stop accessing checkAsUser via RTE in some cases
That seems to add various elog()s which are hit frequently by sqlsmith:
postgres=# select from
(select transaction
from pg_prepared_xacts
right join pg_available_extensions
on false limit 0) where false;
ERROR: permission info at index 2 (with relid=1262) does not match provided RTE (with relid=12081)
postgres=# select from (select confl_tablespace
from pg_stat_database_conflicts
where datname <> (select 'af')
limit 1) where false;
ERROR: invalid perminfoindex 1 in RTE with relid 12271
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2023-02-12 23:58:23 | Re: Making Vars outer-join aware |
| Previous Message | Tom Lane | 2023-02-12 21:13:35 | Re: run pgindent on a regular basis / scripted manner |