X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2236DD1B43A for ; Fri, 5 Dec 2003 17:27:14 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 89434-05 for ; Fri, 5 Dec 2003 13:26:43 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id E993ED1B465 for ; Fri, 5 Dec 2003 13:26:41 -0400 (AST) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 4027472; Fri, 05 Dec 2003 09:27:31 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Jack Coates , Richard Huxton Subject: Re: tuning questions Date: Fri, 5 Dec 2003 09:26:05 -0800 User-Agent: KMail/1.4.3 Cc: pgsql-performance References: <1070553983.6498.52.camel@cletus.lyris.com> <200312042347.54461.dev@archonet.com> <1070584326.18838.235.camel@cletus.lyris.com> In-Reply-To: <1070584326.18838.235.camel@cletus.lyris.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200312050926.05155.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/131 X-Sequence-Number: 4991 Jack, > The frustrating thing is, we also have a UP P3-500 with 512M RAM and two > IDE drives with the same PG install which is doing okay with this load > -- still half the speed of MS-SQL2K, but usable. I'm at a loss. Overall, I'm really getting the feeling that this procedure was optimized for Oracle and/or MSSQL and is hitting some things that aren't such a good idea for PostgreSQL. I highly suggest that you try using log_duration and log_statement (and in 7.4 log_min_duration_statement) to try to locate which particular statements are taking the longest. -- Josh Berkus Aglio Database Solutions San Francisco