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

Page layout footprint

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: heikki(dot)linnakangas(at)enterprisedb(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Page layout footprint
Date: 2008-09-02 12:41:27
Message-ID: 48BD3477.8010100@sun.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi Heikki,

I'm sorry for lack of explanation. It is my fault.

Heikki says (on commit fest wiki):
------------
I believe I debunked this patch enough already. Apparently there's some 
compatibility issue between 32-bit and 64-bit Sparcs, but this patch 
didn't catch that. It doesn't seem like this provides any extra safeness 
or better error messages. If I'm missing something, please provide more 
details on what scenario we currently have a problem, and how this helps 
with it.
------------

The original proposal 
(http://archives.postgresql.org/message-id/489FC8E1.9090307@sun.com)
contains two parts. First part is implementation of --footprint cmd line 
switch which shows you  page layout structures footprint. It is useful 
for development (mostly for in-place upgrade) and also for manual data 
recovery when you need to know exact structures. Second part was add 
this information also into pg_control.file, but how you correctly 
mentioned there is not real use case to do it at this moment.

However, there is still --footprint switch which is useful and it is 
reason why I put it on wiki for review and feedback. The switch could 
also use in build farm for collecting footprints from build farm members.

32/64 bit issue is little bit different story and it is general (not 
only SPARC but on SPARC has bigger impact). Problem is that CRC32 gives 
probably different result when it is compiled 32bit or 64bit. I'm going 
to examine it more.

		Zdenek



Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2008-09-02 12:51:09
Subject: Re: Window functions patch v04 for the September commit fest
Previous:From: Greg SmithDate: 2008-09-02 12:38:11
Subject: Re: posix advises ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group