From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
---|---|
To: | "Hunter Hillegas" <lists(at)lastonepicked(dot)com> |
Cc: | lists(at)lastonepicked(dot)com, nickf(at)ontko(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres 7.2.1 Really Spinning the CPU |
Date: | 2002-06-05 06:09:11 |
Message-ID: | 20020605020911.05193596.nconway@klamath.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 04 Jun 2002 20:20:30 -0700
"Hunter Hillegas" <lists(at)lastonepicked(dot)com> wrote:
> Actually, I may have spoken too soon... It's now back to really spinning the
> CPU...
>
> Any other ideas?
Reading the docs would be a good place to start. Questions like
"It goes slow, what's wrong?" don't give us much to go on.
The query optimizer in 7.2 uses a much richer set of statistics
to aid in choosing the correct query plan. This should lead to
better choices in most situation, but it's conceivable that
you've run into a problem (or at least, a situation in which
7.2 does things differently than 7.1).
I'd suggest finding out which query or queries are taking a while
to execute. Then use EXPLAIN ANALYZE on the query to determine
its query plan (if possible, compare that with the plan chosen
by 7.1). If you can't solve the problem yourself, post the
output of EXPLAIN ANALYZE, as well as any relevant parts of the
schema to the list.
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Mascari | 2002-06-05 06:29:50 | Re: Using C++ with CREATE FUNCTION |
Previous Message | Mike Mascari | 2002-06-05 03:51:27 | Using C++ with CREATE FUNCTION |