Re: Sv: Re: CTE optimization fence - Mailing list pgsql-general

From Adrien NAYRAT
Subject Re: Sv: Re: CTE optimization fence
Date
Msg-id bd64092d-ad4a-9b74-f2f8-ed750347a3dd@anayrat.info
Whole thread Raw
In response to Sv: Re: CTE optimization fence  (Andreas Joseph Krogh <andreas@visena.com>)
Responses Sv: Re: Sv: Re: CTE optimization fence  (Andreas Joseph Krogh <andreas@visena.com>)
List pgsql-general
On 06/27/2018 09:58 AM, Andreas Joseph Krogh wrote:
>      >
>      > but we have to settle on a way of controlling it.
> 
>     +1 from me.
> 
>     I am running more and more into situations where people consider
>     this a bug rather than a feature.
> 
>     FWIW, I think a GUC that switches between the current (mostly
>     unwanted, at least surprising)
>     way and one where the CTE is optimized together with the main query
>     would suit "most" people.
> 
>     For sake of compatibility this could default to the current behaviour
> 
> +1 from me. The default should be "no fence" for sake of least surprise 
> I think. Documenting the change would be sufficient.
> I hope this will be picked up in the comming V12-cycle.


FYI this subject has been discussed in this thread : 
https://www.postgresql.org/message-id/5351711493487900%40web53g.yandex.ru

Regards,


pgsql-general by date:

Previous
From: ERR ORR
Date:
Subject: Re: Code of Conduct committee: call for volunteers
Next
From: Andreas Joseph Krogh
Date:
Subject: Sv: Re: Sv: Re: CTE optimization fence