Re: postgresql +AMD64 +big address spaces - does it work?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andy B" <abhousehuntRE-M--O--V-E(at)blueyonder(dot)co(dot)uk>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: postgresql +AMD64 +big address spaces - does it work?
Date: 2004-07-01 22:52:19
Message-ID: 6827.1088722339@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Andy B" <abhousehuntRE-M--O--V-E(at)blueyonder(dot)co(dot)uk> writes:
> 1. set postgresql.conf->shared_buffers to a value like (40GB/8KB),

That is the very last thing you want to do (even if you could, which you
can't). Let the OS manage the memory --- the kernel can do just fine at
caching large files in RAM. I've never seen any evidence that it helps
to set shared_buffers higher than a few tens of thousands.

See the pgsql-performance archives for much more on this subject.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-07-01 22:59:04 Re: Drop Column with Foreign Key Problem
Previous Message Scott Marlowe 2004-07-01 22:31:13 Re: postgresql +AMD64 +big address spaces - does it work?