diff options
| author | Bruce Momjian <bruce@momjian.us> | 2007-05-05 03:14:40 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2007-05-05 03:14:40 +0000 |
| commit | 71f8127bc677014223d47504c344d73655ad5c8e (patch) | |
| tree | c574081bc0b1547200a390681b67684f59773e7f /doc/FAQ_DEV | |
| parent | d2a4a4069f1677d74267c04d558a8be83a382098 (diff) | |
| download | postgresql-71f8127bc677014223d47504c344d73655ad5c8e.tar.gz postgresql-71f8127bc677014223d47504c344d73655ad5c8e.zip | |
Done:
> * -Allow ORDER BY ... LIMIT # to select high/low value without sort or
<
< Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
< all values to return the high/low value. Instead The idea is to do a
< sequential scan to find the high/low value, thus avoiding the sort.
< MIN/MAX already does this, but not for LIMIT > 1.
<
Diffstat (limited to 'doc/FAQ_DEV')
0 files changed, 0 insertions, 0 deletions