From: Michael Paesold <mpaesold@gmx.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Getting current transaction id
Date: Wed, 25 Sep 2002 22:21:24 +0200
Message-ID: <02b701c264d1$1f3e6340$4201a8c0@beeblebrox> (raw)
References: <3D8F3775.B5DD079@nsd.ca>
<28749.1032797034@www55.gmx.net>
<11493.1032973923@sss.pgh.pa.us>
Tom Lane wrote:
> Michael Paesold <mpaesold@gmx.at> writes:
[snip]
> > If it's not working I will have to implement my own transactions table.
>
> That's what I'd recommend. Transaction IDs are internal to the database
> and are not designed for users to rely on.
>
> regards, tom lane
Well, after reading your explanation I agree with you that it is better
to have my own transaction table. I appreciate your detailed response.
Thanks very much!
Best Regards,
Michael Paesold
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-sql@postgresql.org
Cc: mpaesold@gmx.at, tgl@sss.pgh.pa.us
Subject: Re: Getting current transaction id
In-Reply-To: <02b701c264d1$1f3e6340$4201a8c0@beeblebrox>
* 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