From: Rosser Schwarz <rosser.schwarz@gmail.com>
To: Renato Oliveira <renato.oliveira@grant.co.uk>
Cc: Tino Schwarze <postgresql@tisc.de>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Migrate postgres to newer hardware
Date: Tue, 30 Mar 2010 09:23:49 -0600
Message-ID: <37d451f71003300823n2b9e3707n16676c41cb8883a9@mail.gmail.com> (raw)
In-Reply-To: <7965A9DCF12CC14984420BCC37B1608F25AB1AEE51@Elzar.grant.co.uk>
References: <7965A9DCF12CC14984420BCC37B1608F25AB1AED49@Elzar.grant.co.uk>
<1269959369.15416.5.camel@deimos>
<20100330143831.GE17567@easy5.in-chemnitz.de>
<7965A9DCF12CC14984420BCC37B1608F25AB1AEE51@Elzar.grant.co.uk>
On Tue, Mar 30, 2010 at 8:51 AM, Renato Oliveira
<renato.oliveira@grant.co.uk> wrote:
> If I use postgres 32 bit will it benefit from the extra memory on the system?
Indirectly, yes. No individual PG process will be able to address
more than 4 gbytes of memory. Assuming you have a 64-bit OS living
underneath, however, that may not matter much. You'll potentially be
somewhat constrained in the sane values you can use for shared_buffers
(which, on a 16 gbyte box for example, I'd probably start in the 4
gbyte range and tune from there -- not an option in a 32-bit install).
But leaving aside effective_cache_size (and, as mentioned, potentially
shared_buffers), none of your config values are likely to approach the
4 gbyte boundary -- and in the case of effective_cache_size, that
isn't actually directly addressed by postgres, anyway. It's just used
by the planner to calculate the likelihood of a given page it needs
being in the OS buffer cache, instead of on disk.
I've had production systems with a 32-bit postgres running quite
happily on a 64-bit OS.
rls
--
:wq
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rosser.schwarz@gmail.com, renato.oliveira@grant.co.uk, postgresql@tisc.de
Subject: Re: Migrate postgres to newer hardware
In-Reply-To: <37d451f71003300823n2b9e3707n16676c41cb8883a9@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox