From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Treat <robert@omniti.com>
Cc: pgsql-general@postgresql.org, Amber <guxiaobo1982@hotmail.com>
Cc: Andrew Sullivan <ajs@commandprompt.com>
Subject: Re: PostgreSQL TPC-H test result?
Date: Wed, 10 Sep 2008 10:20:32 +0100
Message-ID: <1221038432.3913.647.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <24765.1220992015@sss.pgh.pa.us>
References: <BLU139-DS5AB90A6E11E3F439F0006CD540@phx.gbl>
<20080909123947.GA59092@commandprompt.com>
<BLU139-DS28D9D90A25BD2AD8CDEF0CD540@phx.gbl>
<200809091129.54467.robert@omniti.com>
<24765.1220992015@sss.pgh.pa.us>
On Tue, 2008-09-09 at 16:26 -0400, Tom Lane wrote:
> That's probably not good because it *looks* like we support the syntax,
> but in fact produce non-spec-compliant results. I think it might be
> better if we threw an error.
Definitely. If we accept SQL Standard syntax like this but then not do
what we should, it is clearly an ERROR. Our reputation will be damaged
if we don't, since people will think that we are blase about standards
compliance and about query correctness. Please lets move swiftly to plug
this hole, as if it were a data loss bug (it is, if it causes wrong
answers to queries for unsuspecting users).
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
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: simon@2ndQuadrant.com, tgl@sss.pgh.pa.us, robert@omniti.com, guxiaobo1982@hotmail.com, ajs@commandprompt.com
Subject: Re: PostgreSQL TPC-H test result?
In-Reply-To: <1221038432.3913.647.camel@ebony.2ndQuadrant>
* 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