Re: A bug in make_outerjoininfo - Mailing list pgsql-hackers

From Richard Guo
Subject Re: A bug in make_outerjoininfo
Date
Msg-id CAMbWs49BXMEvdFM9Uzj-bihDucSQSwFEkpOme_BGo2NpU_Ry=g@mail.gmail.com
Whole thread Raw
In response to Re: A bug in make_outerjoininfo  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: A bug in make_outerjoininfo
List pgsql-hackers

On Wed, Feb 8, 2023 at 7:33 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
We might want to see if we can devise a new example (or wait for
Robins to break it ;-)) before expending a lot of effort on making
the commute_xxx bits more precise.
 
Here is an example that can trigger the same assertion as in bug #17781
with HEAD.  But I haven't got time to look into it, so not sure if it is
the same issue.

select
  coalesce(ref_0.permissive, 'a') as c0
from
 (SELECT pol.polpermissive::text as permissive
   FROM pg_policy pol JOIN pg_class c ON c.oid = pol.polrelid
   LEFT JOIN pg_namespace n ON n.oid = c.relnamespace) as ref_0
 right join pg_catalog.pg_amop as sample_0 on (true)
where (select objsubid from pg_catalog.pg_shdepend) < 1;

Thanks
Richard

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux?
Next
From: Julien Rouhaud
Date:
Subject: Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID