X-Original-To: pgsql-novice-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 053A49FB22F for ; Mon, 7 Aug 2006 17:07:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 61792-01 for ; Mon, 7 Aug 2006 17:07:44 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web51315.mail.yahoo.com (web51315.mail.yahoo.com [206.190.39.125]) by postgresql.org (Postfix) with SMTP id D994D9FB273 for ; Mon, 7 Aug 2006 17:07:41 -0300 (ADT) Received: (qmail 93956 invoked by uid 60001); 7 Aug 2006 20:07:40 -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=04H89KAB/1J/pXgDXh898p5uEqg+nBJKcL/2VysEG9tb97aPAtJTCB8A6i9sHRLnHk72iwV0Dl0RjbmLbQSKAFlFWdnPlAzDRcMnWjCAsyRgXB1OzvHYH6gz1sMTnhB6t2rakzBx22KxiS111B2+CoanKqNs5IEtfDMAhTvkWzE= ; Message-ID: <20060807200740.93954.qmail@web51315.mail.yahoo.com> Received: from [216.199.70.171] by web51315.mail.yahoo.com via HTTP; Mon, 07 Aug 2006 13:07:40 PDT Date: Mon, 7 Aug 2006 13:07:40 -0700 (PDT) From: Saranya Sivakumar Subject: Re: [PERFORM] 7.3.2 pg_restore very slow To: Richard Broersma Jr , pgsqlnovice , pgsqlperform In-Reply-To: <20060807191856.43058.qmail@web31801.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-152457407-1154981260=:92206" Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.43 tagged_above=0 required=5 tests=AWL, BE_BOSS, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS, HTML_MESSAGE X-Spam-Level: *** X-Archive-Number: 200608/59 X-Sequence-Number: 17274 --0-152457407-1154981260=:92206 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi All, Thanks Richard for the additional link. The information is very useful. The restore completed successfully in 2.5 hours in the new 2GB box, with the same configuration parameters. I think if I can tweak the parameters a little more, I should be able to get it down to the 1 hr down time that we can afford. Thanks again for all the help. Sincerely, Saranya Richard Broersma Jr wrote: > 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. --------------------------------- Want to be your own boss? Learn how on Yahoo! Small Business. --0-152457407-1154981260=:92206 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Hi All,
 
Thanks Richard for the additional link. The information is very useful.
 
The restore completed successfully in 2.5 hours in the new 2GB box, with the same configuration parameters. I think if I can tweak the parameters a little more, I should be able to get it down to the 1 hr down time  that we can afford.
 
Thanks again for all the help.
 
Sincerely,
Saranya

Richard Broersma Jr <rabroersma@yahoo.com> wrote:
> 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.

Want to be your own boss? Learn how on Yahoo! Small Business. --0-152457407-1154981260=:92206--