Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: Should we have an optional limit on the recursion depth of recursive CTEs?
Date
Msg-id 9039.1313440295@sss.pgh.pa.us
Whole thread Raw
In response to Should we have an optional limit on the recursion depth of recursive CTEs?  (Peter Geoghegan <peter@2ndquadrant.com>)
Responses Re: Should we have an optional limit on the recursion depth of recursive CTEs?
Re: Should we have an optional limit on the recursion depth of recursive CTEs?
List pgsql-hackers
Tree view 
Peter Geoghegan <peter@2ndquadrant.com> writes:
> Should we have an optional, disabled-by-default limit on the
> recursion/iteration depth of recursive CTEs to guard against stupid
> queries that loop ad infinitum?

I think not ...

> I'd suggest that an appropriate interface would be an int GUC with a
> GucContext of PGC_SUSET, so that DBAs can impose system-wide limits.

... 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?

By and large, this sounds like a solution looking for a problem.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Compressing the AFTER TRIGGER queue
Next
From: Kohei KaiGai
Date:
Subject: [v9.2] DROP statement reworks