| From: | Vincent Roberts <V_Roberts(at)fccc(dot)edu> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Function to detect trigger recursion |
| Date: | 2001-05-16 14:27:41 |
| Message-ID: | 3B028E5D.A8C46985@fccc.edu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello:
Is there a builtin mechanism for detecting trigger recursion or more
specifically
one trigger , causing another tables trigger to fire.
Example:
Table A is updated
Table A's update trigger executes
{
Updates the B table - (maintaining special RI etc.)
Table B's update trigger executes
{
<does some stuff>
<need to know if I was triggered from within another trigger> ?????
( Is there a function that does this? )
<does some more stuff>
}
}
| Attachment | Content-Type | Size |
|---|---|---|
| V_Roberts.vcf | text/x-vcard | 241 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Aughey | 2001-05-16 14:37:25 | Unusual slowdown using subselects |
| Previous Message | Tom Lane | 2001-05-16 13:41:22 | Re: psql always ends with a SEGV: |