| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | eric(at)linux-hw(dot)com (Eric Lee Green) |
| Cc: | scrappy(at)hub(dot)org, jeff(at)remapcorp(dot)com, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] What about LIMIT in SELECT ? |
| Date: | 1998-10-14 00:47:01 |
| Message-ID: | 199810140047.UAA13304@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
> Whereas with the SELECT...LIMIT paradigm, the database engine does NOT
> process the entire huge query, it quits processing once it reaches the
> limit. (Well, at least MySQL does so, if you happen to be using an
> "ORDER BY" supported by an index). Obviously doing 1/4th the work four times
> is better than doing the whole tamale four times :-}.
And no join, I assume.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew N. Dodd | 1998-10-14 06:25:31 | Re: [HACKERS] What about LIMIT in SELECT ? |
| Previous Message | Marc Howard Zuckman | 1998-10-13 23:27:04 | [HACKERS] Alternative to LIMIT in SELECT ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas G. Lockhart | 1998-10-14 01:33:45 | Re: [HACKERS] PostgreSQL v6.4 BETA2 ... |
| Previous Message | Daniele Orlandi | 1998-10-13 23:33:01 | Re: [ADMIN] COPY slows down; is it normal? |