Re: CTE optimization fence on the todo list? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: CTE optimization fence on the todo list?
Date
Msg-id 5544EAAB.8040305@dunslane.net
Whole thread Raw
In response to Re: CTE optimization fence on the todo list?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: CTE optimization fence on the todo list?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 05/01/2015 07:24 PM, Josh Berkus wrote:
> O
>> (A possible compromise position would be to offer a new GUC to
>> enable/disable the optimization globally; that would add only a reasonably
>> small amount of control code, and people who were afraid of the change
>> breaking their apps would probably want a global disable anyway.)
> We'd need the GUC.  I know of a lot of cases where people are using WITH
> clauses specifically to override the query planner, and requiring them
> to edit all of their queries in order to enable the old behavior would
> become an upgrade barrier.
>

+100

This could be a very bad, almost impossible to catch, behaviour break. 
Even if we add the GUC, we're probably going to be imposing very 
significant code audit costs on some users.

cheers

andrew





pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: PATCH: pgbench - logging aggregated info and transactions at the same time
Next
From: Tomas Vondra
Date:
Subject: Re: PATCH: pgbench - merging transaction logs