Re: CTE Materialization

From: Paul van der Linden <paul(dot)doskabouter(at)gmail(dot)com>
To: david(dot)g(dot)johnston(at)gmail(dot)com
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: CTE Materialization
Date: 2021-12-06 20:22:23
Message-ID: CAEC-EqCH7PaJyGNmcVSNw=hR_Ga-q+YL+e2da0AuP75_JUqzeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

It did indeed work as expected.
Took the query down from over 18 hours to 20 minutes, so a huge win!

Paul

On Thu, Dec 2, 2021 at 11:34 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Thursday, December 2, 2021, Paul van der Linden <
> paul(dot)doskabouter(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> when switching to postgres 14 (from 11) I'm having some slow queries
>> because of inlining of CTE's.
>> I know I can get the same result as with PG11 when adding MATERIALIZED to
>> the cte, but the same application also needs to be able to run on older
>> postgres versions, so that is a no-go.
>> Is there any other way that I can have materialized cte's in PG14 while
>> still be compatible with older PG versions?
>> Much appreciated,
>>
>
> The usual anti-inlining hack is to add an “offset 0” to the query.
> Haven’t tried it in 14 myself though.
>
> David J.
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2021-12-07 03:16:27 Re: Query planner issue with preferring primary key over a better index when using ORDER BY and LIMIT
Previous Message Rob Sargent 2021-12-06 19:19:38 Re: Query planner issue with preferring primary key over a better index when using ORDER BY and LIMIT