Re: 32/64-bit transaction IDs?

From: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: 32/64-bit transaction IDs?
Date: 2003-03-21 21:38:12
Message-ID: 200303211438.12046.pgsql@bluepolka.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Friday March 21 2003 11:53, Tom Lane wrote:
> "Ed L." <pgsql(at)bluepolka(dot)net> writes:
> >> XIDs are issued in transaction start order, not transaction commit
> >> order. Dunno if that's what's concerning you.
> >
> > Yes, I'm interested in any reliable ordering of transaction commits for
> > the purpose of serial asyncronous replication. Is that possible?
>
> The order in which commit records are inserted into the WAL log would
> work (and if you just need an ID number, the commit records' WAL-log
> addresses are 64-bits and would serve nicely). But you'll have to add
> code to the backend to get at that.

A 64-bit serial ID number would suffice. I could spend a little time on
that. Any starter hints on files/functions/structure of such an addition?
Something akin to GetTransactionId()?

Ed

In response to

Browse pgsql-general by date

  From Date Subject
Next Message enediel 2003-03-21 21:43:18 partial index
Previous Message Bruce Momjian 2003-03-21 21:16:56 Re: FW: New function - hostmask