| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
| Cc: | Adrien NAYRAT <adrien(dot)nayrat(at)anayrat(dot)info>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Sv: Re: Sv: Re: CTE optimization fence |
| Date: | 2018-06-28 14:54:46 |
| Message-ID: | 20180628145446.3ichhyxb55kbr4x6@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2018-Jun-27, Andreas Joseph Krogh wrote:
> I know. I hate the INLINE proposal and hope default-behaviour will be like in
> other DBs, inline like sub-query as default. GUC for preserving fence is what I
> hope will happen.
I am probably biased ;-) but I like my proposal #1 in this email
https://www.postgresql.org/message-id/20170503173305.fetj4tz7kd56tjlr%40alvherre.pgsql
where you have to mark queries were the current behavior is desired
(WITH MATERIALIZED), and leave all other queries alone. I don't
remember any dissent on that.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-06-28 15:02:10 | Re: could not read block 0 in file : read only 0 of 8192 bytes when doing nasty on immutable index function |
| Previous Message | Niles Oien | 2018-06-28 14:42:15 | Re: plperl and plperlu language extentsions |