| From: | Michael Paesold <mpaesold(at)gmx(dot)at> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Getting current transaction id |
| Date: | 2002-09-23 16:03:54 |
| Message-ID: | 28749.1032797034@www55.gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-sql |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tourtounis Sotiris | 2002-09-23 16:17:51 | Explain analyze time |
| Previous Message | Jean-Luc Lachance | 2002-09-23 15:47:01 | Re: Getting acces to MVCC version number |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-23 16:24:06 | Re: Temp tables and LRU-K caching |
| Previous Message | Mike Mascari | 2002-09-23 15:57:14 | Temp tables and LRU-K caching |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manfred Koizar | 2002-09-23 17:01:01 | Re: [SQL] Monitoring a Query |
| Previous Message | Jean-Luc Lachance | 2002-09-23 15:47:01 | Re: Getting acces to MVCC version number |