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 07:52:58
Message-ID: CAMbWs48t7HjSq+kDmVmX5YKLXtt7ftZ1r8_ByDPXnr0vxkeGuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 8, 2023 at 1:55 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:

>
> 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.
>

Aha, Robins succeeds in breaking it at [1]. It should be the same issue
as reported here. I've looked at it a little bit and concluded my
findings there at [1].

[1]
https://www.postgresql.org/message-id/flat/17781-c0405c8b3cd5e072%40postgresql.org

Thanks
Richard

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2023-02-08 07:59:09 RE: Exit walsender before confirming remote flush in logical replication
Previous Message Michael Paquier 2023-02-08 07:23:34 Re: recovery modules