Re: Setting Shared-Buffers

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Anj Adu <fotographs(at)gmail(dot)com>
Cc: Tino Schwarze <postgresql(at)tisc(dot)de>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Setting Shared-Buffers
Date: 2009-07-11 02:13:27
Message-ID: dcc563d10907101913v7899b7c4p84899e175f1c3e2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Oh wait, that was a different thread. info still holds though.

On Fri, Jul 10, 2009 at 8:04 PM, Scott Marlowe<scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Fri, Jul 10, 2009 at 3:26 PM, Anj Adu<fotographs(at)gmail(dot)com> wrote:
>> You can use upto 64G of RAM on a 32 bit RHEL 5/ Fedora 8 OS using the kernel
>> PAE extension.
>
> And it's about 15% slower, and pgsql itself can only access ~2 or 3G
> shared and 2G per process.  I routinely set shared_buffers to well
> over 3G on big machines, and have a few reporting queries that run
> truly huge work_mem settings.  Really, there's not much reason to be
> running postgresql on 32 bit unix anymore, unless you're stuck using
> an ancient flavor or something.
>
> However, I was referring to Windows, where things are even worse, as
> the OS only sees 3Gigs total cause apparently it doesn't support PAE.
>

--
When fascism comes to America, it will be intolerance sold as diversity.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message sriram.dandapani 2009-07-11 04:27:19 Re: Setting Shared-Buffers
Previous Message Scott Marlowe 2009-07-11 02:04:11 Re: Setting Shared-Buffers