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 15:44:12
Message-ID: 499.1048347852@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:
> create table pg_xlog (
> xid int4 unique not null,
> recno int8 unique not null,
> );
> -- recno = (XLogRecPtr.xlogid) << 32) + XLogRecPtr.xrecoff

> This would map transaction IDs to WAL log record numbers. It seems
> straight-forward to get the right data into this table.

... except that once a transaction has committed, it can't go around
making more database entries. You can only modify the DB within a
transaction.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-03-22 16:02:29 Re: table function: limit, offset, order
Previous Message Ed L. 2003-03-22 15:23:49 Re: 32/64-bit transaction IDs?