Re: Oversight in reparameterize_path_by_child leading to executor crash

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Oversight in reparameterize_path_by_child leading to executor crash
Date: 2023-08-04 00:38:36
Message-ID: CAMbWs4-xG_axH8TUTDLrL43kNK2rQPgXYb4xs6KoEgF9d8CcjA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 3, 2023 at 7:20 PM Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
wrote:

> However, if reparameterization can *not* happen at the planning time, we
> have chosen a plan which can not be realised meeting a dead end. So as long
> as we can ensure that the reparameterization is possible we can delay
> actual translations. I think it should be possible to decide whether
> reparameterization is possible based on the type of path alone. So seems
> doable.
>

That has been done in v2 patch. See the new added function
path_is_reparameterizable_by_child().

Thanks
Richard

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-08-04 00:46:46 Re: Fix incorrect start up costs for WindowAgg paths (bug #17862)
Previous Message Peter Geoghegan 2023-08-04 00:08:50 Re: Use of additional index columns in rows filtering