From: Josh Berkus <josh@agliodbs.com>
To: Jack Coates <jack@lyris.com>
To: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: tuning questions
Date: Fri, 5 Dec 2003 09:26:05 -0800
Message-ID: <200312050926.05155.josh@agliodbs.com> (raw)
In-Reply-To: <1070584326.18838.235.camel@cletus.lyris.com>
References: <1070553983.6498.52.camel@cletus.lyris.com>
<200312042347.54461.dev@archonet.com>
<1070584326.18838.235.camel@cletus.lyris.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, jack@lyris.com, dev@archonet.com
Subject: Re: tuning questions
In-Reply-To: <200312050926.05155.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox