Re: O(N^3) planning time in choose_plan_name() since 8c49a484e8e

From: Manu <manuelreyesbravo(at)gmail(dot)com>
To: Ayoub Kazar <ayoub(dot)kazar(at)data-bene(dot)io>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Robert Haas <rhaas(at)postgresql(dot)org>
Subject: Re: O(N^3) planning time in choose_plan_name() since 8c49a484e8e
Date: 2026-11-01 03:48:21
Message-ID: 179350490113.640844.3138516157039617049@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Ayoub,

On Sun, Nov 1, 2026 at 3:31 AM Ayoub Kazar <ayoub(dot)kazar(at)data-bene(dot)io>
wrote:
> +-- a name of NAMEDATALEN - 1 bytes, used twice
>
> This isn't a concern anymore so we don't need this i think?

Agreed, there are no keys to truncate any more; v5 drops it.

> I guess we should keep this for expr_1_1 case ...

Yes, it is the case where the generated name comes first. v5,
attached, brings it back next to the other two; the code is unchanged.

Regards,
Manu

Attachment Content-Type Size
v5-0001-Avoid-O-N-3-planning-time-in-choose_plan_name.patch text/x-patch 9.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2026-11-01 04:16:45 Re: Row pattern recognition
Previous Message shihao zhong 2026-11-01 03:24:33 Re: First draft of PG 19 release notes