From: siaco@allegro.pl
To: pgsql-performance@postgresql.org
Subject: Re: 7.3 vs 7.2 - different query plan, bad performance
Date: Mon, 16 Jun 2003 08:38:50 +0200
Message-ID: <20030616063850.GA31813@siaco.id.pl> (raw)
In-Reply-To: <ugipevc89eaqk90s23n8kd2iut5uvskpk4@4ax.com>
References: <20030613184506.GE21614@siaco.id.pl>
<ugipevc89eaqk90s23n8kd2iut5uvskpk4@4ax.com>
On Sun, Jun 15, 2003 at 09:48:08PM +0200, Manfred Koizar wrote:
> On Fri, 13 Jun 2003 20:45:06 +0200, Ryszard Lach <siaco@autograf.pl>
> wrote:
> >I have a problem with performance after upgrading from 7.2 to 7.3.
>
> Try
> VACUUM ANALYSE;
>
> and then re-run your query. If it is still slow, post the new EXPLAIN
> ANALYSE output here.
>
Hm. I've tried it too. I don't see a big difference:
siaco=# explain analyze select count(*) from v_c;
QUERY PLAN
---------------------------------------------------------------------------------------------------------------------------
Aggregate (cost=210.83..210.83 rows=1 width=8) (actual time=5418.09..5418.09 rows=1 loops=1)
-> Subquery Scan v_c (cost=28.40..197.63 rows=5281 width=8) (actual time=4.59..5414.13 rows=5281 loops=1)
-> Hash Join (cost=28.40..197.63 rows=5281 width=8) (actual time=4.58..5407.73 rows=5281 loops=1)
Hash Cond: ("outer".id = "inner".id)
-> Seq Scan on b t1 (cost=0.00..76.81 rows=5281 width=4) (actual time=0.01..9.68 rows=5281 loops=1)
-> Hash (cost=24.32..24.32 rows=1632 width=4) (actual time=3.29..3.29 rows=0 loops=1)
-> Seq Scan on a t2 (cost=0.00..24.32 rows=1632 width=4) (actual time=0.01..1.88 rows=1632 loops=1)
SubPlan
-> Aggregate (cost=28.41..28.41 rows=1 width=0) (actual time=1.02..1.02 rows=1 loops=5281)
-> Seq Scan on a t3 (cost=0.00..28.40 rows=3 width=0) (actual time=0.76..1.01 rows=1 loops=5281)
Filter: (parent_id = $0)
Total runtime: 5433.65 msec
--
"First they ignore you. Then they laugh at you. Then they
fight you. Then you win." - Mohandas Gandhi.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: siaco@allegro.pl
Subject: Re: 7.3 vs 7.2 - different query plan, bad performance
In-Reply-To: <20030616063850.GA31813@siaco.id.pl>
References: <20030613184506.GE21614@siaco.id.pl> <ugipevc89eaqk90s23n8kd2iut5uvskpk4@4ax.com> <20030616063850.GA31813@siaco.id.pl>
* 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