X-Original-To: pgsql-novice-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 8B8FE9FA231 for ; Mon, 7 Aug 2006 14:28:33 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 49232-02 for ; Mon, 7 Aug 2006 17:28:27 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web51314.mail.yahoo.com (web51314.mail.yahoo.com [206.190.39.124]) by postgresql.org (Postfix) with SMTP id 43B659FB273 for ; Mon, 7 Aug 2006 14:28:26 -0300 (ADT) Received: (qmail 52232 invoked by uid 60001); 7 Aug 2006 17:28:25 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=S1lnSOApTzlRnzdAxlDqnWd4Ox7HYvx2ox4SyoOyQGr73dhLIR6V6svgxCbRoug6sbCB/pNU+B5/imqeXTGyXUUUrE3IV1cxKHIbRObZ13hidCavVZuWM39cL/copg/qep8HiBCxSLVY2ZloVtOfPYxxfM+G6s0WP+nvMUnCvJE= ; Message-ID: <20060807172825.52230.qmail@web51314.mail.yahoo.com> Received: from [216.199.70.171] by web51314.mail.yahoo.com via HTTP; Mon, 07 Aug 2006 10:28:25 PDT Date: Mon, 7 Aug 2006 10:28:25 -0700 (PDT) From: Saranya Sivakumar Subject: Re: [PERFORM] 7.3.2 pg_restore very slow To: pgsqlnovice , pgsqlperform In-Reply-To: <20060807161715.77647.qmail@web31804.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-2054772213-1154971705=:49605" Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.73 tagged_above=0 required=5 tests=DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, HTML_30_40, HTML_MESSAGE X-Spam-Level: *** X-Archive-Number: 200608/57 X-Sequence-Number: 17272 --0-2054772213-1154971705=:49605 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi Richard, Thank you very much for the information. The SHMMAX was set to 33554432, and that's why it failed to start the postmaster. Thanks for the link to the kernel resources article. I guess changing these parameters would require recompiling the kernel. Is there any work around without changing these parameters to make maximum use of RAM? We got a new server now with 2GB RAM, but it also has the same value for SHMMAX. And I am trying the restore with the following conf sort_mem = 40960 (changed from 1024) shared_buffers = 3000 (changed from 64) max_connections = 128 (changed from 32) Thanks, Saranya Richard Broersma Jr wrote: > IpcMemoryCreate: shmget(key=5432001, size=85450752, 03600) failed: Invalid argument > This error usually means that PostgreSQL's request for a shared memory > segment exceeded your kernel's SHMMAX parameter. You can either > reduce the request size or reconfigure the kernel with larger SHMMAX. > To reduce the request size (currently 85450752 bytes), reduce > PostgreSQL's shared_buffers parameter (currently 10000) and/or > its max_connections parameter (currently 128). > If the request size is already small, it's possible that it is less than > your kernel's SHMMIN parameter, in which case raising the request size or > reconfiguring SHMMIN is called for. if you cat /proc/sys/kernel/shmmax it will tell you what it is set to. It needs to be at least "85450752". The size that Postgresql is trying to grab. also shmall may need to be adjusted also. > The total RAM available on this machine is 512MB. > > I am not sure how to set these parameters SHMMAX and SHMMIN. > Any help/advice would be greatly appreciated. http://www.postgresql.org/docs/8.1/interactive/kernel-resources.html This will help you to set the kernel parameters. Regards, Richard Broersma Jr. --------------------------------- Groups are talking. We´re listening. Check out the handy changes to Yahoo! Groups. --0-2054772213-1154971705=:49605 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Hi Richard,
 
Thank you very much for the information. The SHMMAX was set to 33554432, and that's why it failed to start the postmaster. Thanks for the link to the kernel resources article. I guess changing these parameters would require recompiling the kernel.
 
Is there any work around without changing these parameters to make maximum use of RAM?
 
We got a new server now with 2GB RAM, but it also has the same value for SHMMAX.
 
And I am trying the restore with the following conf
sort_mem = 40960  (changed from 1024)
shared_buffers = 3000 (changed from 64)
max_connections = 128 (changed from 32)
 
Thanks,
Saranya
 
 
 

Richard Broersma Jr <rabroersma@yahoo.com> wrote:
> IpcMemoryCreate: shmget(key=5432001, size=85450752, 03600) failed: Invalid argument
> This error usually means that PostgreSQL's request for a shared memory
> segment exceeded your kernel's SHMMAX parameter. You can either
> reduce the request size or reconfigure the kernel with larger SHMMAX.
> To reduce the request size (currently 85450752 bytes), reduce
> PostgreSQL's shared_buffers parameter (currently 10000) and/or
> its max_connections parameter (currently 128).
> If the request size is already small, it's possible that it is less than
> your kernel's SHMMIN parameter, in which case raising the request size or
> reconfiguring SHMMIN is called for.

if you cat /proc/sys/kernel/shmmax
it will tell you what it is set to. It needs to be at least "85450752". The size that Postgresql
is trying to grab.

also shmall may need to be adjusted also.

> The total RAM available on this machine is 512MB.
>
> I am not sure how to set these parameters SHMMAX and SHMMIN.
> Any help/advice would be greatly appreciated.

http://www.postgresql.org/docs/8.1/interactive/kernel-resources.html
This will help you to set the kernel parameters.

Regards,

Richard Broersma Jr.


Groups are talking. We´re listening. Check out the handy changes to Yahoo! Groups. --0-2054772213-1154971705=:49605--