From: Mischa <mischa.Sandberg@telus.net>
To: pgsql-performance@postgresql.org
Subject: Re: bad performances using hashjoin
Date: Mon, 21 Feb 2005 09:11:34 -0800
Message-ID: <1109005894.421a16469b1c5@webmail.telus.net> (raw)
In-Reply-To: <20287.1108951277@sss.pgh.pa.us>
References: <cv9vbh$1j1o$1@news.hub.org>
<15413.1108925170@sss.pgh.pa.us>
<421939AD2A4.CE73KG@129.180.47.120>
<20287.1108951277@sss.pgh.pa.us>
Quoting Tom Lane <tgl@sss.pgh.pa.us>:
> Klint Gore <kg@kgb.une.edu.au> writes:
> > Is having an order by in a view legal?
>
> Not according to the SQL spec, but PG has allowed it for several releases.
> (The same goes for ORDER BY in a sub-select, which is actually pretty
> much the same thing ...)
Umm... if you implement LIMIT in a subselect, it becomes highly meaningful (nad
useful.
Is this a case of one nonstandard feature being the thin edge of the wedge
for another?
--
"Dreams come true, not free."
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: mischa.Sandberg@telus.net
Subject: Re: bad performances using hashjoin
In-Reply-To: <1109005894.421a16469b1c5@webmail.telus.net>
* 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