Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B0DA32E002D for ; Thu, 20 Mar 2008 11:51:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 76939-05 for ; Thu, 20 Mar 2008 11:51:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by postgresql.org (Postfix) with ESMTP id 44AB52E00A0 for ; Thu, 20 Mar 2008 11:51:36 -0300 (ADT) Received: from mailsrv.i.zmi.at (h081217054243.dyn.cm.kabsi.at [81.217.54.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id CBF3DBD7 for ; Thu, 20 Mar 2008 15:52:10 +0100 (CET) Received: from saturn.i.zmi.at (saturn.i.zmi.at [10.0.0.2]) by mailsrv.i.zmi.at (Postfix) with ESMTP id CFF49BF9A for ; Thu, 20 Mar 2008 15:50:25 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: Windows 64 bit Date: Thu, 20 Mar 2008 15:51:32 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2245279.N47HXSNIyY"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200803201551.32332@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.049 tagged_above=0 required=5 tests=AWL=0.049 X-Spam-Level: X-Archive-Number: 200803/169 X-Sequence-Number: 28652 --nextPart2245279.N47HXSNIyY Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mittwoch, 19. M=E4rz 2008 Campbell, Lance wrote: > Would there be benefits in running PostgreSQL in a 32 bit mode on a > 64 bit version of XP? =A0 My thought is that the OS could access more > of the memory for the caching of the files. =A0I come to this > understanding because on my production Linux box, I don't allocate > more than a 2 Gig to PostgreSQL. =A0I leave the rest of the memory > available for the caching of disk files. =A0So even though PostgreSQL > would be running in a 32 bit mode it seems like it would still run > better on a 64 bit XP box compared to a 32 bit version. =A0This of > course assumes that one does have a sizeable database. If memory is not the problem (db < 2GB), then it depends on your=20 hardware if your specific application is faster with 32 or 64 bit.=20 Handling big data structures that are 64bit aligned on a 64 bit=20 optimized hardware can be slower on a 32bit postgresql, while a=20 database with "small int" only values might actually be faster on a=20 32bit db, because of more efficient caching. Example: We run dbmail (http://www.dbmail.org), a postgresql based=20 e-mail server, with a several GB DB, storing e-mails, which is quite=20 big data in DB terms. 64bit is more efficient here. mfg zmi =2D-=20 // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: www.keyserver.net Key-ID: 1C1209B4 --nextPart2245279.N47HXSNIyY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQBH4nn0zhSR9xwSCbQRAs6rAKDzl3y2hF03byngrde7HT9zZjcwmgCdF03r hH+ugZbKQA1ChN40Fk9NmZ8= =kww3 -----END PGP SIGNATURE----- --nextPart2245279.N47HXSNIyY--