Re: Surviving transaction-ID wraparound, take 2

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Horst Herb <hherb(at)malleenet(dot)net(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Surviving transaction-ID wraparound, take 2
Date: 2001-08-14 12:40:21
Message-ID: 200108141240.f7ECeLm01565@jupiter.us.greatbridge.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Horst Herb <hherb(at)malleenet(dot)net(dot)au> writes:
> > On Tuesday 14 August 2001 02:25, you wrote:
> >> I still think that expanding transaction IDs (XIDs) to 8 bytes is no help.
>
> > But what about all of us who need to establish a true long term audit trail?
> > For us, still the most elegant solution would be a quasi unlimited supply of
> > unique row identifiers. 64 bit would be a huge help (and will be ubiquitous
> > in a few years time anyway).
>
> Uh, that has nothing to do with transaction identifiers ...

And he who needs that kind of long term row identifiers would
be better off with 8-byte sequences anyway - IMNSVHO.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ddkilzer 2001-08-14 13:41:48 Fwd: PostgreSQL Bugzilla
Previous Message mlw 2001-08-14 11:39:57 Re: OID unsigned long long