| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Regina Obe <lr(at)pcorp(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CTE Changes in PostgreSQL 12, can we have a GUC to get old behavior |
| Date: | 2019-02-22 21:30:54 |
| Message-ID: | CA+TgmoYw4M49ATrN0XHKtWO79pqm-H2WAifgUwcnEjsUTVzDsw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 22, 2019 at 4:27 PM Regina Obe <lr(at)pcorp(dot)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 intentionally wrote 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-02-22 21:32:09 | Re: CTE Changes in PostgreSQL 12, can we have a GUC to get old behavior |
| Previous Message | Regina Obe | 2019-02-22 21:27:28 | RE: CTE Changes in PostgreSQL 12, can we have a GUC to get old behavior |