| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, PFC <lists(at)peufeu(dot)com>, C Storm <christian(dot)storm(at)gmail(dot)com> |
| Subject: | Re: pgmemcache |
| Date: | 2006-04-13 00:10:25 |
| Message-ID: | 20060413001024.GP49405@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sriram Dandapani | 2006-04-13 00:32:32 | multi column query |
| Previous Message | Jim Nasby | 2006-04-12 23:03:45 | Re: Better index stategy for many fields with few values |