Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 93A224763B4
	for <pgsql-sql@postgresql.org>; Mon, 23 Sep 2002 12:03:52 -0400 (EDT)
Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100])
	by postgresql.org (Postfix) with SMTP id 365AD4762E3
	for <pgsql-sql@postgresql.org>; Mon, 23 Sep 2002 12:03:51 -0400 (EDT)
Received: (qmail 21511 invoked by uid 0); 23 Sep 2002 16:03:54 -0000
Date: Mon, 23 Sep 2002 18:03:54 +0200 (MEST)
From: Michael Paesold <mpaesold@gmx.at>
To: pgsql-sql@postgresql.org
MIME-Version: 1.0
References: <3D8F3775.B5DD079@nsd.ca>
Subject: Getting current transaction id
X-Priority: 3 (Normal)
X-Authenticated-Sender: #0001946847@gmx.net
X-Authenticated-IP: [194.24.131.244]
Message-ID: <28749.1032797034@www55.gmx.net>
X-Mailer: WWW-Mail 1.5 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200209/270
X-Sequence-Number: 9547

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