X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 962A911F66C2 for ; Wed, 12 Apr 2006 21:35:20 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.241 X-Spam-Level: X-Spam-Status: No, score=-2.241 required=5 tests=[AWL=0.360, BAYES_00=-2.599, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id 9in9ttjD0juL for ; Wed, 12 Apr 2006 21:35:21 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B503E11F65FA for ; Wed, 12 Apr 2006 21:35:17 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k3D0ZEj5006237; Wed, 12 Apr 2006 20:35:14 -0400 (EDT) To: "Jim C. Nasby" cc: Josh Berkus , pgsql-performance@postgresql.org, PFC , C Storm Subject: Re: pgmemcache In-reply-to: <20060413001024.GP49405@pervasive.com> References: <1144135482.063425.33380@z34g2000cwc.googlegroups.com> <20060411225515.GZ49405@pervasive.com> <200604121603.43986.josh@agliodbs.com> <20060413001024.GP49405@pervasive.com> Comments: In-reply-to "Jim C. Nasby" message dated "Wed, 12 Apr 2006 19:10:25 -0500" Date: Wed, 12 Apr 2006 20:35:14 -0400 Message-ID: <6236.1144888514@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200604/281 X-Sequence-Number: 18365 "Jim C. Nasby" writes: > Why are AFTER COMMIT triggers impossible? What happens if such a trigger gets an error? You can't un-commit. regards, tom lane