Re: [PATCHES] WITH RECURSIVE patch V0.1 - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: [PATCHES] WITH RECURSIVE patch V0.1
Date
Msg-id 87hccroafx.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: [PATCHES] WITH RECURSIVE patch V0.1  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: [PATCHES] WITH RECURSIVE patch V0.1
List pgsql-hackers
"Joshua D. Drake" <jd@commandprompt.com> writes:

>> >> Couldn't we just have it pay attention to the existing
>> >> max_stack_depth?
>> >
>> > Recursive query does not consume stack. The server enters an infinite
>> > loop without consuming stack. Stack-depth error does not happen.
>>
>> We could have a separate guc variable which limits the maximum number of
>> levels of recursive iterations. That might be a useful feature for DBAs that
>> want to limit their users from issuing an infinite query.
>
> statement_timeout :)

Good point.

Though it occurs to me that if you set FETCH_COUNT in psql (or do the
equivalent in your code ) statement_timeout becomes much less useful.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's On-Demand Production Tuning

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: [PATCHES] WITH RECURSIVE patch V0.1
Next
From: Hannu Krosing
Date:
Subject: Re: proposal: table functions and plpgsql