public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrei Lepikhov <[email protected]>
To: Richard Guo <[email protected]>
To: PostgreSQL-development <[email protected]>
Cc: Tom Lane <[email protected]>
Subject: Re: Propagate pathkeys from CTEs up to the outer query
Date: Wed, 14 Feb 2024 13:18:02 +0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMbWs49xYd3f8CrE8-WW3--dV1zH_sDSDn-vs2DzHj81Wcnsew@mail.gmail.com>
References: <CAMbWs49xYd3f8CrE8-WW3--dV1zH_sDSDn-vs2DzHj81Wcnsew@mail.gmail.com>

On 29/1/2024 10:18, Richard Guo wrote:
> In [1] we've reached a conclusion that for a MATERIALIZED CTE it's okay
> to 'allow our statistics or guesses for the sub-query to subsequently
> influence what the upper planner does'.  Commit f7816aec23 exposes
> column statistics to the upper planner.  In the light of that, here is a
> patch that exposes info about the ordering of the CTE result to the
> upper planner.
> 
> This patch was initially posted in that same thread and has received
> some comments from Tom in [2].  Due to the presence of multiple patches
> in that thread, it has led to confusion.  So fork a new thread here
> specifically dedicated to discussing the patch about exposing pathkeys
> from CTEs to the upper planner.
I like this approach. It looks good initially, but such features need 
more opinions/views/time to analyse corner cases.
It goes alongside my current backburner - pull parameterisation through 
the GROUP-BY and the query block fence up to the JOIN searching code of 
the parent query.

-- 
regards,
Andrei Lepikhov
Postgres Professional

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Propagate pathkeys from CTEs up to the outer query
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox