From: Jim C. Nasby <jnasby@pervasive.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, PFC <lists@peufeu.com>
Cc: C Storm <christian.storm@gmail.com>
Subject: Re: pgmemcache
Date: Wed, 12 Apr 2006 19:10:25 -0500
Message-ID: <20060413001024.GP49405@pervasive.com> (raw)
In-Reply-To: <200604121603.43986.josh@agliodbs.com>
References: <1144135482.063425.33380@z34g2000cwc.googlegroups.com>
<20060411225515.GZ49405@pervasive.com>
<op.s7vvyggtcigqcu@apollo13>
<200604121603.43986.josh@agliodbs.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jnasby@pervasive.com, josh@agliodbs.com, lists@peufeu.com, christian.storm@gmail.com
Subject: Re: pgmemcache
In-Reply-To: <20060413001024.GP49405@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox