Catch the commit

From: Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Catch the commit
Date: 2005-06-29 22:06:42
Message-ID: 20050630000642.6866d94d.adsmail@wars-nicht.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello,

seems like a complicated question:

is it possible in a module to receive an event, get a trigger fired, get
a function called or something like this when the current transaction is
about to be committed?

Background:
In a module (tablelog) i need the latest possible timestamp before
committing the data for the case, that there is more then one started
transaction. If this happens and the second transaction is commited
first, i have for the time the first transaction is going on invalid
data in my log.

Has anybody an idea about this?

kind regards

--
Andreas 'ads' Scherbaum
Failure is not an option. It comes bundled with your Microsoft product.
(Ferenc Mantfeld)

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-06-29 22:34:42 Re: problem with plpgsql
Previous Message Andreas Pflug 2005-06-29 21:42:33 Re: [HACKERS] Dbsize backend integration