Postgres Pro
Downloads
Home   >   mailing lists

Re: CTE Changes in PostgreSQL 12, can we have a GUC to get old behavior - Mailing list pgsql-hackers

From Robert Haas
Subject Re: CTE Changes in PostgreSQL 12, can we have a GUC to get old behavior
Date
Msg-id CA+TgmoYw4M49ATrN0XHKtWO79pqm-H2WAifgUwcnEjsUTVzDsw@mail.gmail.com
Whole thread Raw
In response to RE: CTE Changes in PostgreSQL 12, can we have a GUC to get old behavior  ("Regina Obe" <lr@pcorp.us>)
List pgsql-hackers
Tree view 
On Fri, Feb 22, 2019 at 4:27 PM Regina Obe <lr@pcorp.us> wrote:
> It's going to make a lot of people hesitant to upgrade if they think they need to revisit every CTE (that they
intentionallywrote cause they thought it would be materialized) to throw in a MATERIALIZED keyword.
 

You might be right, but I hope you're wrong, because if you're right,
then it means that the recent change was ill-considered and ought to
be reverted.  And I think there are a lot of people who are REALLY
looking forward to that behavior change.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: "Regina Obe"
Date:
Subject: RE: CTE Changes in PostgreSQL 12, can we have a GUC to get old behavior
Next
From: Andres Freund
Date:
Subject: Re: CTE Changes in PostgreSQL 12, can we have a GUC to get oldbehavior