Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3A8FA64FCDE for ; Fri, 12 Sep 2008 00:48:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 14962-06 for ; Fri, 12 Sep 2008 00:48:10 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 5B2C164FCBD for ; Fri, 12 Sep 2008 00:48:10 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m8C3m6t3024185; Thu, 11 Sep 2008 23:48:06 -0400 (EDT) To: "Jignesh K. Shah" cc: Greg Smith , Amber , pgsql-performance@postgresql.org Subject: Re: [GENERAL] PostgreSQL TPC-H test result? In-reply-to: <48C9E25F.4070203@sun.com> References: <48C9E25F.4070203@sun.com> Comments: In-reply-to "Jignesh K. Shah" message dated "Thu, 11 Sep 2008 23:30:39 -0400" Date: Thu, 11 Sep 2008 23:48:06 -0400 Message-ID: <24184.1221191286@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/156 X-Sequence-Number: 31469 "Jignesh K. Shah" writes: > * However Empty rows results is occuring consistently > (Infact Q11 also returned empty for me while it worked in their test) > Queries: 4,5,6,10,11,12,14,15 > (ACTION ITEM: I will start separate threads for each of those queries in > HACKERS alias to figure out the problem since it looks like Functional > problem to me and should be interesting to hackers alias) See discussion suggesting that this is connected to misinterpretation of INTERVAL literals. If TPC-H relies heavily on syntax that we'd get wrong, then pretty much every test result has to be under suspicion, since we might be fetching many more or fewer rows than the test intends. I've recently committed fixes that I think would cover this, but you'd really need to compare specific query rowcounts against other DBMSes to make sure we're all on the same page. regards, tom lane