Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id DBF534760D3 for ; Fri, 18 Oct 2002 10:23:06 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id DD501475F4F for ; Fri, 18 Oct 2002 10:23:05 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g9IEMrhR017483; Fri, 18 Oct 2002 10:22:53 -0400 (EDT) To: pgsql@ac6rm.net Cc: pgsql-sql@postgresql.org Subject: Re: TRIGGERed INSERTS In-reply-to: <63387.24.52.245.104.1034949598.squirrel@webmail.ac6rm.net> References: <63387.24.52.245.104.1034949598.squirrel@webmail.ac6rm.net> Comments: In-reply-to "Martin Crundall" message dated "Fri, 18 Oct 2002 06:59:58 -0700" Date: Fri, 18 Oct 2002 10:22:53 -0400 Message-ID: <17482.1034950973@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/211 X-Sequence-Number: 9928 "Martin Crundall" writes: > Some of the data tables have "AFTER INSERT" TRIGGERs on them that, in > turn, insert some subordinate items into parallel data tables and the > central pointer/ordering table. It looks to me like AFTER triggers are fired upon return to the main loop in postgres.c, thus only at the end of a querystring sent by the client. This is perhaps wrong, but I'm not sure that allowing them to fire during plpgsql functions would be a good thing either. regards, tom lane