Catch the commit - Mailing list pgsql-hackers

From Andreas 'ads' Scherbaum
Subject Catch the commit
Date
Msg-id 20050630000642.6866d94d.adsmail@wars-nicht.de
Whole thread Raw
Responses Re: Catch the commit  (Andreas 'ads' Scherbaum <adsmail@wars-nicht.de>)
List 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)


pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: [PATCHES] Dbsize backend integration
Next
From: Tom Lane
Date:
Subject: Re: problem with plpgsql