From: | Larry Rosenman <ler(at)lerctr(dot)org> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, 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:41:59 |
Message-ID: | 20001105094159.A20081@lerami.lerctr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Peter Eisentraut <peter_e(at)gmx(dot)net> [001105 09:39]:
> 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?
Doesn't C99 *REQUIRE* long long? I know the SCO UDK Compiler has had
it for a long time. I know it's early in C99's life, but...
>
> But we could make the XID a struct of two 4-byte integers, at the obvious
> increase in storage size.
What is the difference between a native long long and a struct of 2
long's?
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-11-05 15:42:33 | Re: Transaction ID wraparound: problem and proposed solution |
Previous Message | Larry Rosenman | 2000-11-05 14:15:33 | Re: Summary: what to do about INET/CIDR |