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

From Andrew Dunstan
Subject Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs?
Date
Msg-id 4E4A5344.7040004@dunslane.net
Whole thread Raw
In response to Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs?  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Re: Should we have an optional limit on the recursion depth of recursive CTEs?
List pgsql-hackers

On 08/16/2011 04:56 AM, Magnus Hagander wrote:
> 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?

There is no LIMIT imposed on a query by a server setting, which would be 
the right analogy here.

cheers

andrew


pgsql-hackers by date:

Previous
From: Anssi Kääriäinen
Date:
Subject: Re: index-only scans
Next
From: Heikki Linnakangas
Date:
Subject: Re: WIP: Fast GiST index build