Postgres Pro
Downloads
Home   >   mailing lists

Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs? - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs?
Date
Msg-id CABUevEzCqAzNYUN7ZNmGvrJjqemA6sdUn5r4GokmzxrszLePzw@mail.gmail.com
Whole thread Raw
In response to Re: Should we have an optional limit on the recursion depth of recursive CTEs?  (Greg Stark <stark@mit.edu>)
Responses Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs?
List pgsql-hackers
Tree view 
On Mon, Aug 15, 2011 at 23:49, Greg Stark <stark@mit.edu> wrote:
> On Mon, Aug 15, 2011 at 9:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> ... and that would be a seriously bad API.  There are not SUSET
>> restrictions on other resources such as work_mem.  Why do we need
>> one for this?
>
> I think a better analogy would be imposing a maximum number of rows a
> query can output. That might be a sane thing to have for some
> circumstances but it's not useful in general.

Uh. You mean like LIMIT, which we already have?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Some problems about cascading replication
Next
From: Jeevan Chalke
Date:
Subject: Allowing same cursor name in nested levels