pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dan Langille <dan@langille.org>
To: pgsql-sql <pgsql-sql@postgresql.org>
Subject: why the big difference on this explain analyze?
Date: Sat, 16 Mar 2002 17:07:49 -0500
Message-ID: <20020316220751.A5EE73F28@bast.unixathome.org> (raw)

I was trying to get a query to run.  Yes run.  Not run fast.  Just run.   
;) It was taking far too long.

Here is the before:

explain 
fp2migration=#
fp2migration=# explain
fp2migration-# UPDATE Ports_Check SET found_in_ports = TRUE
fp2migration-#         WHERE EXISTS
fp2migration-#             (   SELECT *
fp2migration(#                   FROM categories, element, ports
fp2migration(#                  WHERE ports.category_id = categories.id
fp2migration(#                    AND ports.element_id  = element.id
fp2migration(#                    AND categories.name   = 
Ports_Check.category_name
fp2migration(#                    AND element.name      = 
Ports_Check.port_name);
NOTICE:  QUERY PLAN:

Seq Scan on ports_check  (cost=0.00..7226574.01 rows=3354 width=27)
  SubPlan
    ->  Hash Join  (cost=103.10..1077.13 rows=1 width=1073)
          ->  Hash Join  (cost=101.47..1075.49 rows=2 width=1030)
                ->  Seq Scan on ports  (cost=0.00..938.99 rows=6999 
width=1000)
                ->  Hash  (cost=101.40..101.40 rows=27 width=30)
                      ->  Index Scan using element_name on element  
(cost=0.00..101.40 rows=27 width=30)
          ->  Hash  (cost=1.62..1.62 rows=1 width=43)
                ->  Seq Scan on categories  (cost=0.00..1.62 rows=1 
width=43)

EXPLAIN

Here is the after:


fp2migration=# explain
fp2migration-# UPDATE Ports_Check SET found_in_ports = TRUE
fp2migration-#         WHERE EXISTS
fp2migration-# ( SELECT *
fp2migration(#                   FROM categories, element, ports, 
Ports_Check
fp2migration(#                  WHERE ports.category_id = categories.id
fp2migration(#                    AND ports.element_id  = element.id
fp2migration(#                    AND categories.name   = 
Ports_Check.category_name
fp2migration(#                    AND element.name      = 
Ports_Check.port_name);
NOTICE:  QUERY PLAN:

Result  (cost=0.00..119.09 rows=6709 width=27)
  InitPlan
    ->  Hash Join  (cost=135.86..39106.26 rows=207 width=1095)
          ->  Nested Loop  (cost=0.00..38403.39 rows=6862 width=1073)
                ->  Nested Loop  (cost=0.00..15811.86 rows=6862 
width=1043)
                      ->  Seq Scan on ports  (cost=0.00..938.99 rows=6999 
width=1000)
                      ->  Seq Scan on categories  (cost=0.00..1.50 rows=50 
width=43)
                ->  Index Scan using element_pkey on element  
(cost=0.00..3.28 rows=1 width=30)
          ->  Hash  (cost=119.09..119.09 rows=6709 width=22)
                ->  Seq Scan on ports_check  (cost=0.00..119.09 rows=6709 
width=22)
  ->  Seq Scan on ports_check  (cost=0.00..119.09 rows=6709 width=27)

EXPLAIN


The difference between the two SQL statements is the inclusion of 
Ports_Check in the WHERE EXISTS select clause.

Would you expect that?

FWIW: I've done a "vacuum full analyze".
-- 
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples




view thread (4+ messages)  latest in thread

Message-ID: <20020316220751.A5EE73F28@bast.unixathome.org>
Permalink:  ../20020316220751.A5EE73F28@bast.unixathome.org/
Also on:    postgresql.org/message-id/20020316220751.A5EE73F28@bast.unixathome.org

 · 

reply

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-sql@postgresql.org
  Cc: dan@langille.org
  Subject: Re: why the big difference on this explain analyze?
  In-Reply-To: <20020316220751.A5EE73F28@bast.unixathome.org>

* 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