Re: Some dead code in get_param_path_clause_serials()

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Some dead code in get_param_path_clause_serials()
Date: 2024-11-14 09:19:46
Message-ID: 70c39150-a1ff-41d2-9b49-4f7507eef0be@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/14/24 08:20, Richard Guo wrote:
> On Wed, Nov 13, 2024 at 9:59 PM Andrei Lepikhov <lepihov(at)gmail(dot)com> wrote:
>> Even So, it would be better to insert changes, induced by new
>> feature by one commit.
>
> I'm not sure I understand what you mean by this sentence.
Yeah, it's my bad English. nothing special, I just wanted to say that
this code can be added later.

>
>> By the way, Do you know if anyone gave a speech on the current state of
>> internal plan parameterisation and its possible development directions?
>> It would be helpful to have such an explanation.
>
> Not that I'm aware of, but I found the "Parameterized Paths" section
> in optimizer/README to be very helpful.
Although parameterisation itself quite clearly described, the concept
and code, related to re-parameterisation (in presence of
inheritance/partitioning) seems complicated.

--
regards, Andrei Lepikhov

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2024-11-14 09:28:17 Re: Converting SetOp to read its two inputs separately
Previous Message Peter Eisentraut 2024-11-14 08:59:07 Re: Remove useless casts to (void *)