Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 14FC947611A for ; Wed, 25 Sep 2002 16:19:25 -0400 (EDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by postgresql.org (Postfix) with SMTP id D81D7476108 for ; Wed, 25 Sep 2002 16:19:23 -0400 (EDT) Received: (qmail 10689 invoked by uid 0); 25 Sep 2002 20:19:24 -0000 Received: from chello062178186201.1.15.tuwien.teleweb.at (HELO beeblebrox) (62.178.186.201) by mail.gmx.net (mp006-rz3) with SMTP; 25 Sep 2002 20:19:24 -0000 Message-ID: <02b701c264d1$1f3e6340$4201a8c0@beeblebrox> From: "Michael Paesold" To: "Tom Lane" Cc: References: <3D8F3775.B5DD079@nsd.ca> <28749.1032797034@www55.gmx.net> <11493.1032973923@sss.pgh.pa.us> Subject: Re: Getting current transaction id Date: Wed, 25 Sep 2002 22:21:24 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/319 X-Sequence-Number: 9596 Tom Lane wrote: > Michael Paesold 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