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=F3pPtd3GHXOm1sVFrXwGZqBsltQdZ4VubE+XgT7kPGTuBjKz4FWWQ+nmqZHkfNzyQvPAo6vdDmvAbvKHDD94WtI5odDyItn5vORKT5WWY9f9+xf6rGieYHXfwIdNvEJsEbKDGJZCtKAZOmYas+Hwjuiwv3HS6/j7tDNrpf1QUUw=
	;
Message-ID: <20060807191856.43058.qmail@web31801.mail.mud.yahoo.com>
Date: Mon, 7 Aug 2006 12:18:56 -0700 (PDT)
From: Richard Broersma Jr <rabroersma@yahoo.com>
Subject: Re: [PERFORM] 7.3.2 pg_restore very slow
To: Saranya Sivakumar <sarlavk@yahoo.com>,
	pgsqlnovice <pgsql-novice@postgresql.org>,
	pgsqlperform <pgsql-performance@postgresql.org>
In-Reply-To: <20060807172825.52230.qmail@web51314.mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

>   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)

This is one of the best links that I can give you in addition to the Postgresql Kernel resource
link.
http://www.powerpostgresql.com/PerfList

I am pretty much a beginner at resource tuning also.  In fact, after googling for sources that
describe how to tune kernel parameters, the postgresql documents remains the best documents I've
found so far.

I would be interested if anyone else on the list knows of any resources or books that have an in
depth discussion on methods/strategies to tune kernel parameters to maximized usage of system
resources and at the same time allow for harmonious sharing between various programs/services.

Regards,

Richard Broersma Jr.