Message-ID: <48E4865F.3010807@archonet.com>
Date: Thu, 02 Oct 2008 09:29:19 +0100
From: Richard Huxton <dev@archonet.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080914)
MIME-Version: 1.0
To: paul@wayr.org
CC: pgsql-performance@postgresql.org
Subject: Re: dedicated server & postgresql 8.1 conf tunning
References: <48E360D0.8080403@archonet.com>
	<6439bfe8d4afed3a360b906353c7e9e5@localhost>
In-Reply-To: <6439bfe8d4afed3a360b906353c7e9e5@localhost>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

paul@wayr.org wrote:
> Thanks,
> 
> Unfornatly, i can't update pgsql to 8.3 since it's not in debian stable.

That's why backports.org was invented :-)
Or does can't mean "not allowed to"?

> So i'm going to play with work_mem & shared_buffers.
> 
> With big shared_buffers pgsql tells me 
> shmget(cle=5432001, taille=11183431680, 03600).
> so i do "echo 13183431680 > /proc/sys/kernel/shmmax" ( 10Go + 2Go just
> in case)
> 
> but pgsql tells me again that it there's not enought shm..
> How can i compute the go shmmax for my server ?

I'm not seeing anything terribly wrong there. Are you hitting a limit
with shmall?

Oh - and I'm not sure there's much point in having more shared-buffers
than you have data.

Try much larger work_mem first, I think that's the biggest gain for you.

-- 
  Richard Huxton
  Archonet Ltd