Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 3F86AF172E1 for ; Wed, 4 Jul 2012 02:19:36 -0300 (ADT) Received: from mail-pb0-f46.google.com ([209.85.160.46]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SmHzy-0004Ch-P8 for pgsql-performance@postgresql.org; Wed, 04 Jul 2012 05:19:35 +0000 Received: by pbbrp8 with SMTP id rp8so10454164pbb.19 for ; Tue, 03 Jul 2012 22:19:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=7EM9ucd6x8pyk9WEXYnApSsZ037HJS7LOC+V/wIq9hY=; b=SKTEhFcciL+6kYJ6/P019+m5/ILTfOsSdhohXtR0TQnAMBkf+EpbH/txMvE62+ljgm HL+SUOQTPYv8cKcel/d1Cfl5mcCnooQg5OZFiXtQ+2QwJv2hTNZ10epVL840B1joM6/z QYEai1Xj147BKK57KuT2BP7H2xw2k3U8W4xyXb3zF1gHUtLd+uc74pVsUIYD4H7epsSJ tI1ys5PqXamCYm2sJu976nVcgLI+znMMdbVY/q193dEwQNHNmJ7Tu0OJ5treF0TZ7Re3 K3m56ty6EdgJ+/t2Cls8DTQYkvs8adejJ3VAdaifmfwvMFiAQVPIy7S00JHI1CN/08FO SzZA== Received: by 10.68.228.102 with SMTP id sh6mr14445799pbc.134.1341379161137; Tue, 03 Jul 2012 22:19:21 -0700 (PDT) Received: from ayaki.localdomain (office1.postnewspapers.com.au. [150.101.171.128]) by mx.google.com with ESMTPS id jp10sm16980374pbb.16.2012.07.03.22.19.17 (version=SSLv3 cipher=OTHER); Tue, 03 Jul 2012 22:19:20 -0700 (PDT) Message-ID: <4FF3D252.4070701@ringerc.id.au> Date: Wed, 04 Jul 2012 13:19:14 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: pgsql-performance@postgresql.org CC: Reza Taheri , "Andy Bond (abond@redhat.com)" , Greg Kopczynski , Jignesh Shah , Greg Smith , Dave Page Subject: Re: Introducing the TPC-V benchmark, and its relationship to PostgreSQL References: <66CE997FB523C04E9749452273184C6C137CB88A82@exch-mbx-113.vmware.com> In-Reply-To: <66CE997FB523C04E9749452273184C6C137CB88A82@exch-mbx-113.vmware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQm2soPAbg/A2GbAiu6DATxriNGTKJCbBT53yuslJlnnISDdLQKgKr4YlF9UIUXE9PByktaO X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/11 X-Sequence-Number: 47192 On 07/04/2012 07:08 AM, Reza Taheri wrote: > ... so the subcommittee moved forward with developing its own > reference kit. The reference kit has been developed to run on > PostgreSQL, and we are focusing our development efforts and testing on > PostgreSQL. That's a very positive step. The TPC seems to me to have a pretty poor reputation among open source database users and vendors. I think that's largely because the schema and tools are typically very closed and restrictively licensed, though the prohibition against publishing benchmarks by big commercial vendors doesn't help. This sounds like a promising change. The TPC benchmarks are really good for load-testing and regression testing, so having one that's directly PostgreSQL friendly will be a big plus, especially if it is appropriately licensed. The opportunity to audit the schema, queries, and test setup before the tool is finalized would certainly be appealing. What can you publish in draft form now? What license terms does the TPC plan to release the schema, queries, and data for TPC-V under? I've cc'd Greg Smith and Dave Page, both of whom I suspect will be interested in this development but could easily miss your message. If you haven't read Greg' book "PostgreSQL High Performance" it's probably a good idea to do so. -- Craig Ringer