From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christian Storm <christian.storm@gmail.com>
Cc: Jim C. Nasby <jnasby@pervasive.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, PFC <lists@peufeu.com>
Subject: Re: pgmemcache
Date: Thu, 13 Apr 2006 13:38:00 -0400
Message-ID: <26792.1144949880@sss.pgh.pa.us> (raw)
In-Reply-To: <4D23826E-7325-4946-B79A-80E321E0E497@gmail.com>
References: <1144135482.063425.33380@z34g2000cwc.googlegroups.com>
<20060411225515.GZ49405@pervasive.com>
<op.s7vvyggtcigqcu@apollo13>
<200604121603.43986.josh@agliodbs.com>
<20060413001024.GP49405@pervasive.com>
<6236.1144888514@sss.pgh.pa.us>
<4D23826E-7325-4946-B79A-80E321E0E497@gmail.com>
Christian Storm <christian.storm@gmail.com> writes:
> Not sure if I follow why this is a problem. Seems like it would be
> beneficial to have both BEFORE and AFTER COMMIT triggers.
> With the BEFORE COMMIT trigger you would have the ability to 'un-
> commit' (rollback) the transaction. With
> the AFTER COMMIT trigger you wouldn't have that option because the
> commit has already been successful. However,
> with an AFTER COMMIT you would be able to trigger other downstream
> events that rely on a transaction successfully committing.
An AFTER COMMIT trigger would have to be in a separate transaction.
What happens if there's more than one, and one of them fails? Even
more to the point, if it's a separate transaction, don't you have
to fire all these triggers again when you commit that transaction?
The idea seems circular.
regards, tom lane
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: tgl@sss.pgh.pa.us, christian.storm@gmail.com, jnasby@pervasive.com, josh@agliodbs.com, lists@peufeu.com
Subject: Re: pgmemcache
In-Reply-To: <26792.1144949880@sss.pgh.pa.us>
* 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