Re: Poor performance using CTE - Mailing list pgsql-performance

From Tom Lane
Subject Re: Poor performance using CTE
Date
Msg-id 3396.1353509947@sss.pgh.pa.us
Whole thread Raw
In response to Re: Poor performance using CTE  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Poor performance using CTE
List pgsql-performance
Andrew Dunstan <andrew@dunslane.net> writes:
> If we're going to do it can we please come up with something more
> intuitive and much, much more documented than "OFFSET 0"? And if/when we
> do this we'll need to have big red warnings all over then release notes,
> since a lot of people I know will need to do some extensive remediation
> before moving to such a release.

The probability that we would actually *remove* that behavior of OFFSET
0 is not distinguishable from zero.  I'm not terribly excited about
having an alternate syntax to specify an optimization fence, but even
if we do create such a thing, there's no need to break the historical
usage.

            regards, tom lane


pgsql-performance by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Poor performance using CTE
Next
From: Andrew Dunstan
Date:
Subject: Re: Poor performance using CTE