pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Gaetano Mendola <mendola@bigfoot.com>
Cc: Dennis Bjorklund <db@zigo.dhs.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: 7.4 vs 7.3 ( hash join issue )
Date: 22 Sep 2004 09:43:24 -0400
Message-ID: <87y8j2ctc3.fsf@stark.xeocode.com> (raw)
In-Reply-To: <4151362C.6070106@bigfoot.com>
References: <4150B096.1050904@bigfoot.com>
	<Pine.LNX.4.44.0409220844010.9559-100000@zigo.dhs.org>
	<4151362C.6070106@bigfoot.com>


Gaetano Mendola <mendola@bigfoot.com> writes:

> hash_join = on
>                 ->  Seq Scan on lookup_tipo_evento le  (cost=0.00..1.16 rows=16 width=32) (actual time=0.017..0.038 rows=16 loops=1)
>
> hash_join = off
>                       ->  Seq Scan on lookup_tipo_evento le  (cost=0.00..1.16 rows=16 width=32) (never executed)


Actually this looks like it's arguably a bug to me. Why does the hash join
execute the sequential scan at all? Shouldn't it also like the merge join
recognize that the other hashed relation is empty and skip the sequential scan
entirely?


-- 
greg




view thread (13+ messages)  latest in thread

Message-ID: <87y8j2ctc3.fsf@stark.xeocode.com>
Permalink:  ../87y8j2ctc3.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87y8j2ctc3.fsf@stark.xeocode.com

 · 

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-performance@postgresql.org
  Cc: gsstark@mit.edu, mendola@bigfoot.com, db@zigo.dhs.org
  Subject: Re: 7.4 vs 7.3 ( hash join issue )
  In-Reply-To: <87y8j2ctc3.fsf@stark.xeocode.com>

* 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