Skip site navigation (1) Skip section navigation (2)

Getting current transaction id

From: Michael Paesold <mpaesold(at)gmx(dot)at>
To: pgsql-sql(at)postgresql(dot)org
Subject: Getting current transaction id
Date: 2002-09-23 16:03:54
Message-ID: 28749.1032797034@www55.gmx.net (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-sql
Hi all,

I just read it's possible to get the MVCC last version numbers. Is it also
possible to get the current transaction id? Would it be possible to check
later if that transaction has been commited? This would be nice for a distributed
application to enforce an "exactly once" semantics for transactions (even if
there are network related errors while the server sends ack for commiting a
transaction).
And if it's possible, how long would that information be valid, i.e. when do
transaction id's get reused?
If it's not working I will have to implement my own transactions table.

Thanks in advance,
Michael Paesold


-- 
Werden Sie mit uns zum "OnlineStar 2002"! Jetzt GMX wählen -
und tolle Preise absahnen! http://www.onlinestar.de


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2002-09-23 16:24:06
Subject: Re: Temp tables and LRU-K caching
Previous:From: Mike MascariDate: 2002-09-23 15:57:14
Subject: Temp tables and LRU-K caching

pgsql-sql by date

Next:From: Manfred KoizarDate: 2002-09-23 17:01:01
Subject: Re: [SQL] Monitoring a Query
Previous:From: Jean-Luc LachanceDate: 2002-09-23 15:47:01
Subject: Re: Getting acces to MVCC version number

pgsql-general by date

Next:From: Tourtounis SotirisDate: 2002-09-23 16:17:51
Subject: Explain analyze time
Previous:From: Jean-Luc LachanceDate: 2002-09-23 15:47:01
Subject: Re: Getting acces to MVCC version number

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group