Re: MemoizePath fails to work for partitionwise join

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: MemoizePath fails to work for partitionwise join
Date: 2022-12-06 01:58:01
Message-ID: CAMbWs48Gi9RB9E=A6yFAJZfB4A_OA9OWNUPUkzz64edPyeqiJg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 6, 2022 at 1:42 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> One small problem is that top_parent doesn't exist in the back branches,
> so I had to substitute a much uglier lookup in order to make this work
> there. I'm surprised that we got away without top_parent for this long
> TBH, but anyway this fix validates the wisdom of 2f17b5701.
>
> So, pushed with some cosmetic adjustments and the modified back-branch
> code.

Thanks for the modifying and pushing and the back-patching. I didn't
realize how the fix should look like if without top_parent. Thanks to
the work in 2f17b5701, it makes life much easier.

Thanks
Richard

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-12-06 02:23:23 Re: Error-safe user functions
Previous Message Melanie Plageman 2022-12-06 01:49:20 Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)