Received: from magus.postgresql.org ([87.238.57.229])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <andrew@dunslane.net>) id 1TbGBd-0002R0-6V
	for pgsql-performance@postgresql.org; Wed, 21 Nov 2012 19:42:17 +0000
Received: from relay3-d.mail.gandi.net ([217.70.183.195])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <andrew@dunslane.net>) id 1TbGBb-0001dm-K7
	for pgsql-performance@postgresql.org; Wed, 21 Nov 2012 19:42:16 +0000
X-Originating-IP: 217.70.178.130
Received: from mfilter1-d.gandi.net (mfilter1-d.gandi.net [217.70.178.130])
	by relay3-d.mail.gandi.net (Postfix) with ESMTP id 6AE83A809E;
	Wed, 21 Nov 2012 20:42:04 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter1-d.gandi.net
Received: from relay3-d.mail.gandi.net ([217.70.183.195])
	by mfilter1-d.gandi.net (mfilter1-d.gandi.net [10.0.15.180])
	(amavisd-new, port 10024)
	with ESMTP id NloXBoJy1o8Y; Wed, 21 Nov 2012 20:42:03 +0100 (CET)
X-Originating-IP: 98.27.58.255
Received: from [192.168.10.146] (cpe-098-027-058-255.nc.res.rr.com
	[98.27.58.255]) (Authenticated sender: adsend@dunslane.net)
	by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 94260A8094;
	Wed, 21 Nov 2012 20:42:01 +0100 (CET)
Message-ID: <50AD2E88.4000902@dunslane.net>
Date: Wed, 21 Nov 2012 14:42:00 -0500
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: Gavin Flower <GavinFlower@archidevsys.co.nz>
CC: Heikki Linnakangas <hlinnakangas@vmware.com>,
	Andres Freund <andres@anarazel.de>,
	Tom Lane <tgl@sss.pgh.pa.us>, Craig Ringer <craig@2ndQuadrant.com>,
	Claudio Freire <klaussfreire@gmail.com>,
	Merlin Moncure <mmoncure@gmail.com>,
	David Greco <David_Greco@harte-hanks.com>,
	"pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Poor performance using CTE
References: 
 <CAHyXU0xeEVX2P=HaNxPiKayEhkWp3GobgAXCQPrfsqbawXVV-w@mail.gmail.com>
	<CAGTBQpZ_Za-XSXvmPUx3F7wgeX=HB1xUpDsn+1DXY3a87YJLBQ@mail.gmail.com>
	<CAHyXU0z4oUss50vhH_wGZ-HERQe9wCMSf1nMTGNddXeCoKvVVA@mail.gmail.com>
	<CAGTBQpbf9bdJ3gjcYdw2FuPmN=dqx+wE7opsCp515cEndpGDYw@mail.gmail.com>
	<50AC1472.3050607@2ndQuadrant.com>
	<18123.1353455585@sss.pgh.pa.us> <50ACD166.1000507@vmware.com>
	<50ACE970.7050701@dunslane.net> <3396.1353509947@sss.pgh.pa.us>
	<50ACF16C.2020902@dunslane.net>
	<20121121153209.GA1271@awork2.anarazel.de>
	<50ACF658.10902@archidevsys.co.nz> <50ACF991.3020603@vmware.com>
	<50AD2BD1.8070206@archidevsys.co.nz>
In-Reply-To: <50AD2BD1.8070206@archidevsys.co.nz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -2.6 (--)
X-Archive-Number: 201211/246
X-Sequence-Number: 48612


On 11/21/2012 02:30 PM, Gavin Flower wrote:
> WITH FENCE foo AS (SELECT ...)
> default?
>
>
> WITHOUT FENCE foo AS (SELECT ...)     :-)
> Nah!
> I prefer this, but it is too specific to 'WITH',
> and very unSQL standardish!
>
> Alternatively one of the following
>
>  1. WITH UNFENCED foo AS (SELECT ...)
>  2. WITH NO FENCE foo AS (SELECT ...)
>  3. WITH NOT FENCE foo AS (SELECT ...)
>
> I loke the firsat variant, but the 3rd is
> most SQL standardish!
>

As Tom (I think) pointed out, we should not have a syntax tied to CTEs.

cheers

andrew