Re: max_stack_depth Exceeded - Mailing list pgsql-general

From Magnus Hagander
Subject Re: max_stack_depth Exceeded
Date
Msg-id 48C0EF63.9050406@hagander.net
Whole thread Raw
In response to max_stack_depth Exceeded  (Ow Mun Heng <Ow.Mun.Heng@wdc.com>)
Responses Re: max_stack_depth Exceeded
List pgsql-general
Ow Mun Heng wrote:
> Hi,
>
> I'm playing around with triggers to implement partitioning.
> I hit something which I don't know what and I don't have internet here
> at work to find out what is the cause.
>
>
> ERROR : stack depth limit exceeded
>
> I see that this is one of the options in postgresql.conf but I don't
> know exactly what it is.

Sounds like you may have created a situation with infinite recursion.

Like in some branch your trigger is inserting back into the parent
table, thus firing the trigger again in an endless loop, instead of
inserting it into the proper child table.

//Magnus


pgsql-general by date:

Previous
From: Ow Mun Heng
Date:
Subject: max_stack_depth Exceeded
Next
From: Ow Mun Heng
Date:
Subject: Re: max_stack_depth Exceeded