X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 9E82A11F65DD for ; Wed, 12 Apr 2006 21:10:27 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.434 X-Spam-Level: X-Spam-Status: No, score=0.434 required=5 tests=[AWL=0.434] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id nViq28-jt9pL for ; Wed, 12 Apr 2006 21:10:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 81B9311F6069 for ; Wed, 12 Apr 2006 21:10:24 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 3A9E556435; Wed, 12 Apr 2006 19:10:26 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Wed, 12 Apr 2006 19:10:25 -0500 Date: Wed, 12 Apr 2006 19:10:25 -0500 From: "Jim C. Nasby" To: Josh Berkus Cc: pgsql-performance@postgresql.org, PFC , C Storm Subject: Re: pgmemcache Message-ID: <20060413001024.GP49405@pervasive.com> References: <1144135482.063425.33380@z34g2000cwc.googlegroups.com> <20060411225515.GZ49405@pervasive.com> <200604121603.43986.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604121603.43986.josh@agliodbs.com> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060413:josh@agliodbs.com::vVeUt/aWs9adZlc8:00000000000000000000 0000000000000000000000001lYE X-Hashcash: 1:20:060413:pgsql-performance@postgresql.org::kCf3vwcjBYzC82tg:00000 0000000000000000000000002LV9 X-Hashcash: 1:20:060413:lists@peufeu.com::QtCpotrhVZMrBNPw:00x7r X-Hashcash: 1:20:060413:christian.storm@gmail.com::5ZLvkdjD3SkPM9Pq:000000000000 0000000000000000000000005t5a X-Archive-Number: 200604/279 X-Sequence-Number: 18363 On Wed, Apr 12, 2006 at 04:03:43PM -0700, Josh Berkus wrote: > PFC, > > > It would be nice to have ON COMMIT triggers for this use. > > > > However you can emulate ON COMMIT triggers with a modification of the > > memcache update process : > > Well, I'm back in touch with the GORDA project so possibly we can have > BEFORE COMMIT triggers after all. > > BTW, it's important to note that AFTER COMMIT triggers are logically > impossible, so please use BEFORE COMMIT so that it's clear what we're > talking about. Why are AFTER COMMIT triggers impossible? ISTM they would be useful as a means to indicate to some external process if a transaction succeeded or not. And for some things you might only want to fire the trigger after you knew that the transaction had committed. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461