pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jean-Luc Lachance <jllachan@nsd.ca>
To: pgsql-sql@postgresql.org
Subject: performance on update table from a join
Date: Tue, 30 Apr 2002 16:34:36 -0400
Message-ID: <3CCEFFDC.516131CC@nsd.ca> (raw)
References: <20020430181519.5E5D9475985@postgresql.org>
	<21326.1020191577@sss.pgh.pa.us>
	<21413.1020192353@sss.pgh.pa.us>
	<21990.1020197073@sss.pgh.pa.us>


I am updating a large (1M+) table from a join.  There is no question the
table has to be sequencially scanned. But, I am surprised that Postgres
would perform the join in order to do the update.

My take is that it should lookup in the "rs" table for a match and then
from this reduced set lookup the "routes" table.

Since it is performing an update, it is fair to assume that there will
be only one record from "routes" that will match the where clause. So,
why waste resources performing the join first?

Or maybe I am not reading the query plan correctly...

THX


nsd=# explain update c set newroute = r.route, route = r.routeno, street
= trim( lpad( r.seqno, 4, '0')), exchangeno = r.exchangeno
nsd-# from routes r, rs s where ( c.stname, c.municipality) =
(s.oldstname, s.oldmuni) and
nsd-# (s.exchangeno, s.stname, s.municipality) = ( r.exchangeno,
r.street, r.municipality) and
nsd-# r.fromno <= c.civic and c.civic <= r.tono and (r.parity =
c.civic%2 or r.parity = -1);
NOTICE:  QUERY PLAN:
 
Hash Join  (cost=109.44..118460.53 rows=1 width=857)
  ->  Seq Scan on c  (cost=0.00..112409.04 rows=1156604 width=519)
  ->  Hash  (cost=109.44..109.44 rows=1 width=338)
        ->  Merge Join  (cost=0.00..109.44 rows=1 width=338)
              ->  Index Scan using routes_str_mun on routes r 
(cost=0.00..52.00 rows=1000 width=152)
              ->  Index Scan using rs_stname on rs s  (cost=0.00..52.00
rows=1000 width=186)
 
EXPLAIN



view thread (5+ messages)  latest in thread

Message-ID: <3CCEFFDC.516131CC@nsd.ca>
Permalink:  ../3CCEFFDC.516131CC@nsd.ca/
Also on:    postgresql.org/message-id/3CCEFFDC.516131CC@nsd.ca

 · 

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: jllachan@nsd.ca
  Subject: Re: performance on update table from a join
  In-Reply-To: <3CCEFFDC.516131CC@nsd.ca>

* 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