Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 661AA475B04 for ; Tue, 30 Apr 2002 16:50:05 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 169A84759A6 for ; Tue, 30 Apr 2002 16:50:04 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3UKnuF00756; Tue, 30 Apr 2002 16:49:56 -0400 (EDT) To: Jean-Luc Lachance Cc: pgsql-sql@postgresql.org Subject: Re: performance on update table from a join 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> Comments: In-reply-to Jean-Luc Lachance message dated "Tue, 30 Apr 2002 16:34:36 -0400" Date: Tue, 30 Apr 2002 16:49:56 -0400 Message-ID: <753.1020199796@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/368 X-Sequence-Number: 7632 Jean-Luc Lachance 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