Re: BUG #4748: hash join and sort-merge join make different results

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Roman Kononov <kononov(at)ftml(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4748: hash join and sort-merge join make different results
Date: 2009-04-03 20:18:25
Message-ID: 21648.1238789905@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Dickson S. Guedes" <listas(at)guedesoft(dot)net> writes:
> I could reproduce this once in a database that already have a table
> named "t", then after i did dropped it i couldn't anymore.

As noted, you might have to force use of a hash join (my machine
preferred a mergejoin before the ANALYZE and a nestloop after).
It's definitely broken :-(

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Roman Kononov 2009-04-04 03:52:52 Re: BUG #4748: hash join and sort-merge join make different results
Previous Message Tom Lane 2009-04-03 19:57:48 Re: BUG #4748: hash join and sort-merge join make different results