Re: 32/64-bit transaction IDs? - Mailing list pgsql-general

From Ed L.
Subject Re: 32/64-bit transaction IDs?
Date
Msg-id 200303221137.37759.pgsql@bluepolka.net
Whole thread Raw
In response to Re: 32/64-bit transaction IDs?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 32/64-bit transaction IDs?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Saturday March 22 2003 11:29, Tom Lane wrote:
> "Ed L." <pgsql@bluepolka.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.

Why not?  How would you replay them on the slave in the same transaction
groupings and order that occurred on the master?


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: 32/64-bit transaction IDs?
Next
From: Dennis Gearon
Date:
Subject: Re: configuration according to the database