Re: allowing extensions to control planner behavior

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: allowing extensions to control planner behavior
Date: 2024-10-23 11:46:58
Message-ID: CA+TgmobH2CyoVuNOmzZarspGYbLEtjLax3FgP1ubrAo2tqhvxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 23, 2024 at 11:51 AM Andrei Lepikhov <lepihov(at)gmail(dot)com> wrote:
> Parse tree may be implemented with multiple execution plans. Even
> clauses can be transformed during optimisation (Remember OR -> ANY).
> Also, the cardinality of a middle-tree join depends on the inner and
> outer subtrees. Because of that, having a hash on RelOptInfo's relids
> and restrictions + hashes of child RelOptInfos and carrying it through
> all other stages up to the end of execution is the most stable approach
> I know.

I'm not saying there's a better way to do it today. I'm saying I think
there SHOULD be a better way to do it.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bill Smith 2024-10-23 12:25:11 Re: msvc directory missing in PostgreSQL 17.0
Previous Message Amit Kapila 2024-10-23 10:08:03 Re: Make default subscription streaming option as Parallel