From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
---|---|
To: | "Zdenek Kotala" <Zdenek(dot)Kotala(at)Sun(dot)COM> |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: PageLayout footprint |
Date: | 2008-08-11 14:07:20 |
Message-ID: | 48A04798.80603@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zdenek Kotala wrote:
> It is what I don't know. controlfile only says "incorrect checksum in
> control file". It seems to me that CRC computing does not work
> correctly. I check pg_control footprint and it is same for 32/64. It
> seems to me a false positive complain, but ...
Endianness perhaps? Per comment in ControlFileData:
> * This data is used to check for hardware-architecture compatibility of
> * the database and the backend executable. We need not check endianness
> * explicitly, since the pg_control version will surely look wrong to a
> * machine of different endianness, but we do need to worry about MAXALIGN
> * and floating-point format. (Note: storage layout nominally also
> * depends on SHORTALIGN and INTALIGN, but in practice these are the same
> * on all architectures of interest.)
> Footprint switch should help show you why it is incompatible and also
> protect you during development to break some structure.
Apparently the footprint switch didn't provide any insight into the
Sparc 32/64-bit issue, so I'm not too impressed..
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2008-08-11 14:13:15 | Re: proposal: UTF8 to_ascii function |
Previous Message | Zdenek Kotala | 2008-08-11 13:48:41 | Re: Proposal: PageLayout footprint |