From: | Nicolai Petri <lists(at)petri(dot)cc> |
---|---|
To: | "Marko Kreen" <markokr(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Getting current transaction id |
Date: | 2006-07-27 19:50:19 |
Message-ID: | 200607272150.19800.lists@petri.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tuesday 25 July 2006 22:05, Marko Kreen wrote:
> On 7/24/06, Nicolai Petri <lists(at)petri(dot)cc> wrote:
> > I'm in the need for my custom written replication engine to obtain the
> > current transaction id from a trigger function. As far as I'm told it's
> > not possible today. Would people object much if this functionality was
> > added for 8.2 ?
>
> Using XID directly has some drawbacks, I need similary finctionality,
> and decided to extend XID to 8-bytes and use that externally:
>
> http://archives.postgresql.org/pgsql-patches/2006-07/msg00157.php
>
> Would that work for you?
That seems perfect for my use - I solved the wraparound issue in my code by
only allowing pending transactions to stay in the queue for 1 month maximum.
But I'll probably use the 64 bit counter instead if it was present.
Is there any chance for this going into 8.2 ?
---
Nicolai Petri
From | Date | Subject | |
---|---|---|---|
Next Message | Mónica Ivonne Herrera Alonso | 2006-07-27 19:50:35 | Re: About "ALTER USER" command |
Previous Message | Rocco Altier | 2006-07-27 19:48:20 | Re: [COMMITTERS] pgsql: another try at keeping AIX/ppc happy on cube test. |