Re: Transaction ID wraparound: problem and proposed solution

From: Larry Rosenman <ler(at)lerctr(dot)org>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, 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 21:24:47
Message-ID: 20001105152447.A4628@lerami.lerctr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Hannu Krosing <hannu(at)tm(dot)ee> [001105 15:21]:
> Peter Eisentraut wrote:
> >
> I suspect that we do on many platforms (like *BSD, Linux and Win32).
Many, but not *ALL*. I prefer to build my stuff using the Native
UnixWare 7 (UDK) Compiler. As of the Feature Supplement (due out any
week now, I have a pre-release), we have WORKING C++, and the compiler
is C99, and the C++ is STD C++ (very very very close).

GCC/G++ for this platform (at least from the SCO Skunkware side) is
NOT C99 nore STD C++.

>
> What platforms we currently support don't have functional gcc ?
>
> > But we could make the XID a struct of two 4-byte integers, at the obvious
> > increase in storage size.
>
> And a (hopefully) small performance hit on operations when defined as
> macros,
> and some more for less data fitting in cache.
>
> what operations do we need to be defined ?
>
> will >, <, ==, !=, >=, <== and ++ be enough ?
>
> -------------
> Hannu
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vadim 2000-11-05 22:50:19 pgsql/src/backend/access/transam (xact.c xlog.c)
Previous Message Larry Rosenman 2000-11-05 20:59:00 Re: Transaction ID wraparound: problem and proposed solution