| From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
|---|---|
| To: | Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | chris(at)bitmead(dot)com, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Solution for LIMIT cost estimation |
| Date: | 2000-02-15 01:00:12 |
| Message-ID: | 3.0.1.32.20000214170012.00efc5a0@mail.pacifier.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 02:43 AM 2/15/00 +0200, Hannu Krosing wrote:
>Don Baccus wrote:
>> Well...personally I don't see LIMIT as being particularly harmful,
>> and it is a convenience. Remember, for the web space you're speaking
>> of keeping overhead low is a real concern, and requiring a series
>> of queries where currently only one needed will probably go over like
>> a lead ballon.
>
>I meant that the _backend_ could (in some distant future, when the
>optimiser is perfect :) implement LIMIT as above sequence.
Oops! Sorry...at the moment I'm near to loathing the very existence
of LIMIT so misunderstood :)
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Baccus | 2000-02-15 01:07:08 | Re: [HACKERS] Solution for LIMIT cost estimation |
| Previous Message | Hiroshi Inoue | 2000-02-15 01:00:04 | RE: [HACKERS] Solution for LIMIT cost estimation |