Re: max_stack_depth Exceeded

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Ow Mun Heng <Ow(dot)Mun(dot)Heng(at)wdc(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: max_stack_depth Exceeded
Date: 2008-09-05 08:35:47
Message-ID: 48C0EF63.9050406@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ow Mun Heng 2008-09-05 08:58:20 Re: max_stack_depth Exceeded
Previous Message Ow Mun Heng 2008-09-05 08:03:13 max_stack_depth Exceeded