Re: max_stack_depth Exceeded

From: "Ow Mun Heng" <ow(dot)mun(dot)heng(at)wdc(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Magnus Hagander" <magnus(at)hagander(dot)net>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: max_stack_depth Exceeded
Date: 2008-09-06 00:13:55
Message-ID: 88C32A5D9FC71B4BB1B911B7B21049691300302F@wdmyexbe03.my.asia.wdc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Friday, September 05, 2008 11:22 PM
To: Magnus Hagander
Cc: Ow Mun Heng; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] max_stack_depth Exceeded

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Ow Mun Heng wrote:
>> Am I doing something wrong?

> If your trigger is defined on the head_raw_all_test_2 table, then yes.
> Because it will do a new insert there, and the new insert will fire the
> trigger again, which will do a new insert, which wil lfire the trigger
etc.

>>Of course, the way to have the row be inserted into the parent table is
>>to just let the trigger return it, instead of returning null.

Er.. which is how? I'm new in this so, syntax would be appreciated.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2008-09-06 02:25:58 Re: log_statement not working on pl/pgsql functions
Previous Message Anderson dos Santos Donda 2008-09-05 19:52:52 Error Installing Postgre 8.3 Silent Mod