X-Original-To: pgsql-sql@postgresql.org
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 92028474E4F
	for <pgsql-sql@postgresql.org>; Thu, 13 Feb 2003 16:11:47 -0500 (EST)
Received: from news.hub.org (news.hub.org [64.49.215.80])
	by postgresql.org (Postfix) with ESMTP id 2A3E4474E42
	for <pgsql-sql@postgresql.org>; Thu, 13 Feb 2003 16:11:47 -0500 (EST)
Received: by news.hub.org (Postfix, from userid 8)
	id 136EA43A971; Thu, 13 Feb 2003 16:11:47 -0500 (EST)
From: Dmitry Tkach <dmitry@openratings.com>
X-Newsgroups: comp.databases.postgresql.sql
Subject: Re: Debugging postmaster to fix possible bug in Postgres? Followup
Date: Thu, 13 Feb 2003 17:50:22 -0500
Organization: Hub.Org Networking Services (http://www.hub.org)
Lines: 22
Message-ID: <3E4C212E.2080805@openratings.com>
References: <44sn4vgisulljq45qo35bug12sed1ll3ce@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@news.hub.org
To: Manfred Koizar <mkoi-pg@aon.at>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
In-Reply-To: <44sn4vgisulljq45qo35bug12sed1ll3ce@4ax.com>
To: pgsql-sql@postgresql.org
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200302/299
X-Sequence-Number: 11697


> 
> SQL92 says:
>     <direct select statement: multiple rows> ::=
>          <query expression> [ <order by clause> ]
>     [...]
>     3) Let T be the table specified by the <query expression>.
> 
>     4) If ORDER BY is specified, then each <sort specification> in the
>        <order by clause> shall identify a column of T.
> 

Then it looks like postgres behaviour is still not compliant, if I read it correctly, because

select x from mytable order by y;

should be invalid according to this, but works just fine in postres.

Dima.

P.S. I think, this is a great feature actually (missed it a lot in informix), so, I hope, you guys won't start discussing how to fix it :-)