pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joachim Zobel <jzobel@heute-morgen.de>
To: Marek Lewczuk <newsy@lewczuk.com>
Cc: Lista dyskusyjna pgsql-general <pgsql-general@postgresql.org>
Subject: Re: Get current trasanction id
Date: Tue, 28 Dec 2004 16:05:53 +0100
Message-ID: <1104246353.22419.216.camel@localhost> (raw)
In-Reply-To: <41D06889.9040503@lewczuk.com>
References: <41CFCD69.6010503@lewczuk.com>
	<20041227145406.GA73681@winnie.fuhr.org>
	<41D06889.9040503@lewczuk.com>

Am Mo, den 27.12.2004 schrieb Marek Lewczuk um 20:54:
> Michael Fuhr napisaƂ(a):
> > Why do you want the transaction ID?  What problem are you trying
> > to solve?
> > 
> I've already solved the problem - I found somewhere on the web a very 
> simple C function, which returns transaction id. I need transaction id 
> for plperl functions setVar, getVar (using $_SHARED array). Functions 
> can write/read variables which are available either for connection or 
> transaction.

It would be nice to have that in pgplsql. I once needed a transaction Id
in oracle for a historisation trigger. It saves before copies of the
modified records on a per transaction basis.

Sincerely,
Joachim

--
 
"... ein Geschlecht erfinderischer Zwerge, die fuer alles gemietet werden 
koennen."                            - Bertolt Brecht - Leben des Galilei 




view thread (7+ messages)  latest in thread

Message-ID: <1104246353.22419.216.camel@localhost>
Permalink:  ../1104246353.22419.216.camel@localhost/
Also on:    postgresql.org/message-id/1104246353.22419.216.camel@localhost

 · 

reply

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: jzobel@heute-morgen.de, newsy@lewczuk.com, pgsql-general@postgresql.org
  Subject: Re: Get current trasanction id
  In-Reply-To: <1104246353.22419.216.camel@localhost>

* 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