Re: Making Vars outer-join aware
От | Justin Pryzby |
---|---|
Тема | Re: Making Vars outer-join aware |
Дата | |
Msg-id | 20230213184807.GF1653@telsasoft.com обсуждение исходный текст |
Ответ на | Re: Making Vars outer-join aware (Richard Guo <guofenglinux@gmail.com>) |
Ответы |
Re: Making Vars outer-join aware
|
Список | pgsql-hackers |
On Mon, Feb 13, 2023 at 03:33:15PM +0800, Richard Guo wrote: > On Mon, Feb 13, 2023 at 7:58 AM Justin Pryzby <pryzby@telsasoft.com> wrote: > > The patch broke this query: > > > > select from pg_inherits inner join information_schema.element_types > > right join (select from pg_constraint as sample_2) on true > > on false, lateral (select scope_catalog, inhdetachpending from > > pg_publication_namespace limit 3); > > ERROR: could not devise a query plan for the given query > BTW, here is a simplified query that can trigger this issue on HEAD. > > select * from t1 inner join t2 left join (select null as c from t3 left > join t4 on true) as sub on true on true, lateral (select c, t1.a from t5 > offset 0 ) ss; It probably doesn't need to be said that the original query was reduced from sqlsmith... But I mention that now to make it searchable. Thanks, -- Justin
В списке pgsql-hackers по дате отправления: