Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 3C29D9FB500 for ; Sat, 16 Jun 2007 00:04:12 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 33426-09 for ; Sat, 16 Jun 2007 00:04:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from oxford.xeocode.com (unknown [87.127.95.194]) by postgresql.org (Postfix) with ESMTP id 2BC6E9FB4EC for ; Sat, 16 Jun 2007 00:04:06 -0300 (ADT) Received: from localhost.enta.net ([127.0.0.1] helo=oxford.xeocode.com) by oxford.xeocode.com with esmtp (Exim 4.67) (envelope-from ) id 1HzOZz-0001Gm-Ro; Sat, 16 Jun 2007 04:03:59 +0100 From: Gregory Stark To: "chester c young" Cc: "sql pgsql" Subject: Re: trigger firing order In-Reply-To: <466219.19714.qm@web54302.mail.re2.yahoo.com> (chester c. young's message of "Fri, 15 Jun 2007 19:08:13 -0700 (PDT)") Organization: EnterpriseDB References: <466219.19714.qm@web54302.mail.re2.yahoo.com> X-Draft-From: ("nnimap+mail01.enterprisedb.com:INBOX.sql" 373) Date: Sat, 16 Jun 2007 04:03:59 +0100 Message-ID: <87abv0ppls.fsf@oxford.xeocode.com> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/114 X-Sequence-Number: 28604 "chester c young" writes: > tables A and B: a post row trigger on A cause updates on B which has > its own post row trigger. > > does the post trigger on A wait until post trigger on B is executed? - > this seems intuitive to me. How can it wait until the trigger on B is executed if the trigger on B doesn't actually get triggered until someone updates B and it's the trigger on A doing the update? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com