Re: pgmemcache - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: pgmemcache
Date
Msg-id 20060413001024.GP49405@pervasive.com
Whole thread Raw
In response to Re: pgmemcache  (Josh Berkus <josh@agliodbs.com>)
Responses Re: pgmemcache
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: pgmemcache
Next
From: "Sriram Dandapani"
Date:
Subject: multi column query