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

Jean-Luc Lachance <jllachan@nsd.ca> writes:
> 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)

Have you vacuum analyzed routes and rs?  I always disbelieve any plan
with 'rows=1000' in it, because I know that's the default assumption
when no stats are available...

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <753.1020199796@sss.pgh.pa.us>
Permalink:  ../753.1020199796@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/753.1020199796@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, jllachan@nsd.ca
  Subject: Re: performance on update table from a join
  In-Reply-To: <753.1020199796@sss.pgh.pa.us>

* 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