Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Database file compatability


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
  • Cc: pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: Database file compatability
  • Date: Tue, 27 Sep 2005 23:27:52 -0400
  • Message-id: <1223(dot)1127878072(at)sss(dot)pgh(dot)pa(dot)us>

"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> writes:
> I think all ALIGNOF macros should be checked.

There are no platforms for which ALIGNOF_SHORT is different from 2.
I don't think there are any platforms we care about where ALIGNOF_INT
is different from 4.  The cases of interest are ALIGNOF_DOUBLE,
ALIGNOF_LONG, ALIGNOF_LONG_LONG_INT (note that MAXIMUM_ALIGNOF is
just the largest of these).  In practice "long int" is the same type
as either "int" or "long long int", so ALIGNOF_LONG isn't a distinct
case either.  What it comes down to is that MAXIMUM_ALIGNOF is
sufficient to tell the difference between the platforms we need to
deal with.  If you have a counterexample, tell us about it.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group