Re: A bug in make_outerjoininfo

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A bug in make_outerjoininfo
Date: 2023-02-08 05:55:10
Message-ID: CAMbWs49BXMEvdFM9Uzj-bihDucSQSwFEkpOme_BGo2NpU_Ry=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 8, 2023 at 7:33 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2023-02-08 06:33:16 Re: possible proposal plpgsql GET DIAGNOSTICS oid = PG_ROUTINE_OID
Previous Message Andres Freund 2023-02-08 05:44:47 Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux?