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

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

Hi Andreas,

On Fri, Nov 20, 2026 at 1:36 PM UTC, Andreas <andreasfe(at)pm(dot)me> wrote:
> As far as I see, your hash table idea would solve both cases for us.

That hash table is what v6 does, posted on 4 November:
https://postgr.es/m/179382931036.1743405.1568941311065599844@gmail.com

It applies to master and REL_19_STABLE as of today. If you can plan
your statement with it, the numbers against 18.7 would show whether
it is enough for 19.

Regards,
Manu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2026-11-20 14:41:58 Re: reindexdb: Change quoting rule of --schema?
Previous Message Greg Burd 2026-11-20 14:21:53 Re: Hash index inserts serialise on the metapage tuple counter