Re: Transaction ID wraparound: problem and proposed solution

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transaction ID wraparound: problem and proposed solution
Date: 2000-11-05 15:42:33
Message-ID: Pine.LNX.4.21.0011051638470.780-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hannu Krosing writes:

> > The first thought that comes to mind is that XIDs should be promoted to
> > eight bytes. However there are several practical problems with this:
> > * portability --- I don't believe long long int exists on all the
> > platforms we support.
>
> I suspect that gcc at least supports long long on all OS-s we support

Uh, we don't want to depend on gcc, do we?

But we could make the XID a struct of two 4-byte integers, at the obvious
increase in storage size.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-05 18:02:37 Re: Transaction ID wraparound: problem and proposed solution
Previous Message Larry Rosenman 2000-11-05 15:41:59 Re: Transaction ID wraparound: problem and proposed solution