Re: 32/64-bit transaction IDs?

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

"Ed L." <pgsql(at)bluepolka(dot)net> writes:
> Actually, dbmirror does it in a couple of steps, but I think this is the
> basic idea. So the queued tuple changes are groupable (and thus
> replayable) by xid and order of queueing. Then the slave gets them in the
> hopefully-correct order via
> select ...
> from queue q
> where q.xid is in some appropriate range
> order by xid asc, tuple_id asc;

I think this last part is wrong. It shouldn't be using the xid as part
of the ordering, only the sequence value.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ed L. 2003-03-22 18:37:37 Re: 32/64-bit transaction IDs?
Previous Message Ed L. 2003-03-22 18:25:59 Re: 32/64-bit transaction IDs?