Re: Transaction ID wraparound: problem and proposed solution - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Transaction ID wraparound: problem and proposed solution
Date
Msg-id Pine.LNX.4.21.0011051638470.780-100000@peter.localdomain
Whole thread Raw
In response to Re: Transaction ID wraparound: problem and proposed solution  (Hannu Krosing <hannu@tm.ee>)
Responses Re: Transaction ID wraparound: problem and proposed solution
List 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@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Transaction ID wraparound: problem and proposed solution
Next
From: Larry Rosenman
Date:
Subject: Re: Transaction ID wraparound: problem and proposed solution