| From: | Terry Mackintosh <terry(at)terrym(dot)com> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] What about LIMIT in SELECT ? |
| Date: | 1998-10-14 17:33:33 |
| Message-ID: | Pine.LNX.3.95.981014132744.14397C-100000@terry1.acun.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 13 Oct 1998, Bruce Momjian wrote:
> See the fetch manual page.<P>
OK, I will.
> This only prevents all row results from being transfered to the client.
Yes, this is good, but this is only half the problem ...
> The entire query must be evaluated, even if you only want just the first
... this is the other half.
> few rows. Consider a query that has an order by. There is no way
> to return any rows until the entire query is evaluated and sorted.
This is where I was hoping one of you guru types might have some insight,
-- how to stop short a query at X rows, even if it has an order by.
No way?
Terry Mackintosh <terry(at)terrym(dot)com> http://www.terrym.com
sysadmin/owner Please! No MIME encoded or HTML mail, unless needed.
Proudly powered by R H Linux 4.2, Apache 1.3, PHP 3, PostgreSQL 6.3
-------------------------------------------------------------------
Success Is A Choice ... book by Rick Patino, get it, read it!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Terry Mackintosh | 1998-10-14 17:41:24 | Re: [HACKERS] What about LIMIT in SELECT ? |
| Previous Message | Terry Mackintosh | 1998-10-14 17:21:51 | Re: [HACKERS] What about LIMIT in SELECT ? |