From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | salah jubeh <s_jubeh(at)yahoo(dot)com> |
Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: stack depth limit exceeded |
Date: | 2011-03-31 16:41:27 |
Message-ID: | 87ipuzqm2w.fsf@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
salah jubeh <s_jubeh(at)yahoo(dot)com> writes:
> Hello,
>
> I have written this function which is simply returns the entities which depends on a certain entity. It works fine if the
> dependency tree is not long. However, If I have an entity which are linked to many other entities I get
>
> stack depth limit exceeded
> HINT: Increase the configuration parameter "max_stack_depth", after ensuring the platform's stack depth limit is adequate.
>
> I wrote this function to know exactly what are the tables, views that will be doped if I use cascade option. I want to get
> around this issue without changing the server configuration
[snip]
I'd strongly suspect a case of infinite recursion. Have you ruled that
out first?>
You might try incrementing a sequence in the function during one of the
bad runs to see how deep it's recursing.
--
Jerry Sievers
Postgres DBA/Development Consulting
e: gsievers19(at)comcast(dot)net
p: 305.321.1144
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Clark | 2011-03-31 16:56:45 | 7.4 quoting |
Previous Message | Gurjeet Singh | 2011-03-31 16:35:09 | Re: stack depth limit exceeded |