Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 27B439FBB43 for ; Wed, 4 Apr 2007 19:54:24 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 62858-02-2 for ; Wed, 4 Apr 2007 19:54:20 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by postgresql.org (Postfix) with SMTP id 5B5A69FBB0F for ; Wed, 4 Apr 2007 19:53:39 -0300 (ADT) Received: (qmail invoked by alias); 04 Apr 2007 22:53:28 -0000 Received: from xdsl-87-79-195-130.netcologne.de (EHLO colt.pezone.net) [87.79.195.130] by mail.gmx.net (mp028) with SMTP; 05 Apr 2007 00:53:28 +0200 X-Authenticated: #495269 X-Provags-ID: V01U2FsdGVkX1+roupIZ+2rsmRbhu8eZ90UUYvFkvcps17CvXwvZH +uz/veqGTpA9ng From: Peter Eisentraut To: pgsql-admin@postgresql.org Subject: Re: How to compile with different MAXALIGN? Date: Thu, 5 Apr 2007 00:53:17 +0200 User-Agent: KMail/1.9.5 Cc: Sean Murphy References: <4614186B.2060101@equipoint.com> In-Reply-To: <4614186B.2060101@equipoint.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704050053.17612.peter_e@gmx.net> X-Y-GMX-Trusted: 0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/50 X-Sequence-Number: 25114 Sean Murphy wrote: > search of the Docs tells me that I can compile the server with a > different MAXALIGN, but the install docs don't give any indication > how this is achieved. Is there a configure or gmake option I can > feed, or do I need to change a line in one (or more) of the source > files? Alignment is a property dictated by the compiler, so the official way to change that is to argue with your compiler. On Linux i386, it seems that the option -malign-double will get you the 8 byte alignment that might be compatible with your Windows build. All of this, however, is totally unofficial and highly risky, because an alignment difference might indicate that there are other differences in the binary data layout that are not caught by the existing checks. You will get data corruption if you are wrong. Moreover, a build with a nonstandard alignment will be incompatible with everything else on your system in ways that are hard to define in brief, so interfacing with other libraries or modules will possibly be broken, as will your next PostgreSQL upgrade. -- Peter Eisentraut http://developer.postgresql.org/~petere/