Re: max_stack_depth Exceeded - Mailing list pgsql-general

From Ow Mun Heng
Subject Re: max_stack_depth Exceeded
Date
Msg-id 88C32A5D9FC71B4BB1B911B7B21049691300302F@wdmyexbe03.my.asia.wdc.com
Whole thread Raw
In response to Re: max_stack_depth Exceeded  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general

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

Magnus Hagander <magnus@hagander.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.


pgsql-general by date:

Previous
From: "Anderson dos Santos Donda"
Date:
Subject: Error Installing Postgre 8.3 Silent Mod
Next
From: Bruce Momjian
Date:
Subject: Re: log_statement not working on pl/pgsql functions