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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Manu <manuelreyesbravo(at)gmail(dot)com>, 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-10-28 17:31:05
Message-ID: 1676407.1793208665@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Hm. What if we instead just switched to something like using
> list_length(glob->subplanNames) as a suffix once the list gets long enough?

Or just do it that way always. I think the requirement here is only
uniqueness and reproducibility.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-28 18:32:44 Re: [(known) BUG] DELETE/UPDATE more than one row in partitioned foreign table
Previous Message Bharath Rupireddy 2026-10-28 17:22:47 Re: Parallel vacuum: check XID wraparound failsafe between indexes