X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 371FD536A5 for ; Mon, 18 Apr 2005 03:11:51 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 74861-09 for ; Mon, 18 Apr 2005 06:11:42 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id DF25E53875 for ; Mon, 18 Apr 2005 03:11:38 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j3I6BZSE014025; Mon, 18 Apr 2005 02:11:35 -0400 (EDT) To: Steve Poe Cc: "Nurlan Mukhanov (AL/EKZ)" , pgsql-performance@postgresql.org Subject: Re: Postgresql works too slow In-reply-to: <426348BD.3040002@sfnet.cc> References: <70E6659A9338D8418379B4EC0CA5819137928D@erumomw002.eemea.ericsson.se> <426348BD.3040002@sfnet.cc> Comments: In-reply-to Steve Poe message dated "Sun, 17 Apr 2005 22:42:21 -0700" Date: Mon, 18 Apr 2005 02:11:35 -0400 Message-ID: <14024.1113804695@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/385 X-Sequence-Number: 11782 Steve Poe writes: > Try enabliing your checkpoint_segments. In my example, our database > restore took 75mins. After enabling checkpoints_segments to 20, we cut > it down to less than 30 minutes. Increasing maintenance_work_mem might help too ... or several other settings ... with no information about exactly *what* is slow, it's hard to say. regards, tom lane