On Wed, Nov 21, 2012 at 1:35 PM, Andrew Dunstan <and...@dunslane.net> wrote: >>>> Why syntax? What about a guc? >>>> >>>> collapse_cte_limit? >>> >>> Because there are very good reasons to want to current behaviour. A guc >>> is a global either/or so I don't see it helping much. >> >> set collapse_cte_limit=8; >> with blah as (blah) select blah; >> >> Not global at all. >> > > Then you have to unset it again, which is ugly. You might even want it > applying to *part* of a query, not the whole thing, so this strikes me as a > dead end.
Really? Because I've seen here people that want it generally (because Oracle/MSSQL/your favourite db does it), and people that don't want it (generally because they need it). I haven't seen any mention to mixing fenced and unfenced usage. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
