| From: | Joachim Zobel <jzobel(at)heute-morgen(dot)de> |
|---|---|
| To: | Marek Lewczuk <newsy(at)lewczuk(dot)com> |
| Cc: | Lista dyskusyjna pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Get current trasanction id |
| Date: | 2004-12-28 15:05:53 |
| Message-ID: | 1104246353.22419.216.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre-Frédéric Caillaud | 2004-12-28 15:09:59 | Re: running a query file of 42MB |
| Previous Message | Vivek Khera | 2004-12-28 15:01:20 | Re: Long-running performance (MVCC, Vacuum, etc.) - Any fix? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marek Lewczuk | 2004-12-28 15:51:36 | Re: Get current trasanction id |
| Previous Message | Dennis Sacks | 2004-12-28 00:20:06 | simulating global temp tables in plpgsql functions |