From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Valery Popov <v(dot)popov(at)postgrespro(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PROPOSAL] Max recursion depth in WITH Queries (Common Table Expressions) |
Date: | 2015-10-28 07:58:58 |
Message-ID: | CAFj8pRAWKKfb=R9BiNvauuLM1EuE_Jf7ojaQ_-taZ-LfZ3cwDA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-10-28 8:33 GMT+01:00 Valery Popov <v(dot)popov(at)postgrespro(dot)ru>:
> Hi, Hackers
>
> Recursive queries are typically used to deal with hierarchical or
> tree-structured data.
> In some conditions when data contain relationships with cycles recursive
> query will loop
> unlimited and significantly slows the client's session.
> To prevent "infinite" loop I suggest the max_recursion_depth parameter,
> which defines the maximum recursion level during the execution of recursive
> query.
> When max_recursion_depth > 0 and the recursion level of query exceeds
> specified value then the execution of query interrupts with error message.
> In the MS SQL Server there is MAXRECURSION hint for the same purpose.
>
>
+1
good idea
Regards
Pavel
>
> Thanks!
> --
>
> Regards,
> Valery Popov
> Postgres Professional http://www.postgrespro.com
> The Russian Postgres Company
>
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Victor Wagner | 2015-10-28 08:18:39 | Re: Patch: Implement failover on libpq connect level. |
Previous Message | Dmitry Voronin | 2015-10-28 07:44:37 | pg_dump |