From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitry Tkach <dmitry@openratings.com>
Cc: Manfred Koizar <mkoi-pg@aon.at>
Cc: pgsql-sql@postgresql.org
Subject: Re: Debugging postmaster to fix possible bug in Postgres? Followup
Date: Thu, 13 Feb 2003 18:48:29 -0500
Message-ID: <2032.1045180109@sss.pgh.pa.us> (raw)
In-Reply-To: <3E4C212E.2080805@openratings.com>
References: <44sn4vgisulljq45qo35bug12sed1ll3ce@4ax.com>
<3E4C212E.2080805@openratings.com>
Dmitry Tkach <dmitry@openratings.com> writes:
> 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.
Yup, it's an extension --- as indeed is pointed out at the bottom of our
SELECT reference page. But it's a well-defined extension, because every
row of the result does have a clearly associated value of y. Once you
throw in GROUP BY or aggregates, you can't order by values that aren't
constrained by the grouping.
regards, tom lane
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, dmitry@openratings.com, mkoi-pg@aon.at
Subject: Re: Debugging postmaster to fix possible bug in Postgres? Followup
In-Reply-To: <2032.1045180109@sss.pgh.pa.us>
* 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