Date: Tue, 09 Sep 2008 18:28:54 -0400
From: "Jignesh K. Shah" <J.K.Shah@Sun.COM>
Subject: Re: PostgreSQL TPC-H test result?
In-reply-to: <Pine.GSO.4.64.0809091723090.29002@westnet.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Amber <guxiaobo1982@hotmail.com>,
	pgsql-general <pgsql-general@postgresql.org>
Message-id: <48C6F8A6.6070308@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <BLU139-DS5AB90A6E11E3F439F0006CD540@phx.gbl>
	<Pine.GSO.4.64.0809091723090.29002@westnet.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)


Greg Smith wrote:
> On Tue, 9 Sep 2008, Amber wrote:
>
>> I read something from 
>> http://monetdb.cwi.nl/projects/monetdb/SQL/Benchmark/TPCH/index.html 
>> saying that PostgreSQL can't give the correct result of the some 
>> TPC-H queries
>
> Jignesh Shah at Sun ran into that same problem.  It's mentioned 
> briefly in his presentation at 
> http://blogs.sun.com/jkshah/entry/postgresql_east_2008_talk_postgresql 
> on pages 26 and 27.  5 of the 22 reference TCP-H queries (4, 5, 6, 10, 
> 14) returned zero rows immediately for his tests.  Looks like the 
> MonetDB crew is saying it does that on queries 4,5,6,10,12,14,15 and 
> that 20 takes too long to run to generate a result.  Maybe 12/15/20 
> were fixed by changes in 8.3, or perhaps there were subtle errors 
> there that Jignesh didn't catch--it's not like he did a formal 
> submission run, was just kicking the tires.  I suspect the difference 
> on 20 was that his hardware and tuning was much better, so it probably 
> did execute fast enough.
>
> While some of the MonetDB bashing in this thread was unwarranted, it 
> is quite inappropriate that they published performance results here.  
> Would be nice if someone in the community were to grab ahold of the 
> TPC-H problems and try to shake them out.
>

Hmm This is the second time MonetDB has published PostgreSQL numbers. I 
think I will try to spend few days on TPC-H again on a much smaller 
scale (to match what MonetDB used) and start discussions on solving the 
problem.. Keep tuned.

Regards,
Jignesh