Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 104026505C7 for ; Sun, 13 Jul 2008 15:05:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 30408-05 for ; Sun, 13 Jul 2008 15:05:46 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 28EF86505C6 for ; Sun, 13 Jul 2008 15:05:48 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m6DI5i55012345; Sun, 13 Jul 2008 14:05:44 -0400 (EDT) To: Zdenek Kotala cc: Heikki Linnakangas , Pavan Deolasee , PostgreSQL-patches Subject: Re: page macros cleanup (ver 04) In-reply-to: <4874C09F.4000302@sun.com> References: <48529B83.9010907@sun.com> <2e78013d0807030450m4cab60d0jd99d1acce59fae56@mail.gmail.com> <486DD1D1.50604@sun.com> <2e78013d0807040150w393ad72codaf06a6ac12a83ce@mail.gmail.com> <486DF644.4070604@enterprisedb.com> <2e78013d0807040350m3b2913cfkceaa70d8f9d697c2@mail.gmail.com> <486E01B0.9050100@enterprisedb.com> <2e78013d0807040404q5ff7f7faq9f87a39e0f0552fa@mail.gmail.com> <486E138F.4060900@sun.com> <4874A6E0.9070909@enterprisedb.com> <4874C09F.4000302@sun.com> Comments: In-reply-to Zdenek Kotala message dated "Wed, 09 Jul 2008 15:43:59 +0200" Date: Sun, 13 Jul 2008 14:05:44 -0400 Message-ID: <12344.1215972344@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/142 X-Sequence-Number: 6836 Zdenek Kotala writes: > Good catch. if we have to bump catalog version then I have there small patch > which introduce following macro and remove PageHeaderData stucture from > HashMetaPageData: Seems like a bad idea --- PageGetContents is not guaranteed to deliver a maxaligned pointer, so at least in principle this could result in alignment violations. It would accidentally fail to fail as of CVS HEAD, but any future rearrangement of PageHeaderData or HashMetaPageData could create a problem. (Possibly PageGetContents *should* guarantee a maxaligned result, but the current coding does not.) regards, tom lane