Re: CTE inlining

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>, Ilya Shkuratov <motr(dot)ilya(at)ya(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CTE inlining
Date: 2017-05-01 04:22:50
Message-ID: CAFj8pRAFWxQTQJJ5Fr3F85oFWATTyHt0BoU+0-pXsO6u0nUviA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2017-05-01 1:21 GMT+02:00 Andres Freund <andres(at)anarazel(dot)de>:

> On 2017-04-30 07:19:21 +0200, Pavel Stehule wrote:
> > why we cannot to introduce GUC option - enable_cteoptfence ?
>
> Doesn't really solve the issue, and we've generally shied away from GUCs
> that influence behaviour after a few bad experiences. What if you want
> one CTE inlined, but another one not?
>

It change behave in same sense like enable_nestloop, enable_hashjoin, ...
with same limits.

Regards

Pavel

>
> - Andres
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2017-05-01 04:48:47 Re: OK, so culicidae is *still* broken
Previous Message Amit Langote 2017-05-01 04:18:31 Re: Declarative partitioning - another take