Re: [HACKERS] CTE inlining - Mailing list pgsql-hackers

From Oleg Bartunov
Subject Re: [HACKERS] CTE inlining
Date
Msg-id CAF4Au4x1WfsuwK2au9UACemar2ZkkCyp8TfA0mTXE3MRgvcaMA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] CTE inlining  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Mon, May 1, 2017 at 7:22 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>
>
> 2017-05-01 1:21 GMT+02:00 Andres Freund <andres@anarazel.de>:
>>
>> On 2017-04-30 07:19:21 +0200, Pavel Stehule wrote:
>> > why we cannot to introduce GUC option - enable_cteoptfence ?
>>
>> Doesn't really solve the issue, and we've generally shied away from GUCs
>> that influence behaviour after a few bad experiences.  What if you want
>> one CTE inlined, but another one not?
>
>
> It change behave in same sense like enable_nestloop, enable_hashjoin, ...
> with same limits.

And then we recall  plan hints :)

>
> Regards
>
> Pavel
>
>>
>>
>> - Andres
>
>



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] UPDATE of partition key
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] logical replication syntax (was DROP SUBSCRIPTION, query cancellations and slot handling)