pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: 7.4 vs 7.3 ( hash join issue )
Date: Thu, 23 Sep 2004 16:04:20 +0200
Message-ID: <4152D7E4.3010409@bigfoot.com> (raw)
In-Reply-To: <14106.1095875794@sss.pgh.pa.us>
References: <Pine.LNX.4.44.0409221717010.9559-100000@zigo.dhs.org>
<87sm9acih3.fsf@stark.xeocode.com>
<14106.1095875794@sss.pgh.pa.us>
Tom Lane wrote:
> Greg Stark <gsstark@mit.edu> writes:
>
>>No, postgres didn't do things in reverse order. It hashed the empty table and
>>then went ahead and checked every record of the non-empty table against the
>>empty hash table.
>
>
>>Reading the code there's no check for this, and it seems like it would be a
>>useful low-cost little optimization.
>
>
> Yeah, I was just looking at doing that.
>
> It would also be interesting to prefetch one row from the outer table and fall
> out immediately (without building the hash table) if the outer table is
> empty. This seems to require some contortion of the code though :-(
>
>
>>I think postgres normally hashes the table it thinks is smaller,
>
>
> Right, it will prefer to put the physically smaller table (estimated
> width*rows) on the inside.
Do you plan to do a patch for the 7.4, so I'll wait for a 7.4.6 ( that IIRC have already
two important patches pending ) or is 8.0 stuff ?
Regards
Gaetano Mendola
view thread (13+ messages)
Message-ID: <4152D7E4.3010409@bigfoot.com> Permalink: ../4152D7E4.3010409@bigfoot.com/ Also on: postgresql.org/message-id/4152D7E4.3010409@bigfoot.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: mendola@bigfoot.com, tgl@sss.pgh.pa.us Subject: Re: 7.4 vs 7.3 ( hash join issue ) In-Reply-To: <4152D7E4.3010409@bigfoot.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