As this came up in a work situation, I was wondering a little bit
about the top-k issue. Right now, top-k is implemented (most easily,
I think) via a SELECT with a LIMIT and no OFFSET. 3 questions arise
1. Are there currently any optimizations specific to top-k in
PostgreSQL? If so, what are they?
2. What kinds of top-k optimizations *can't* be part of PostgreSQL
(things that would break MVCC, e.g.)?
3. What kinds of top-k optimizations might (eventually) be included
Hoping this stimulates some friendly & informative discussion... :)
David Fetter david(at)fetter(dot)org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
pgsql-hackers by date
|Next:||From: Marc G. Fournier||Date: 2005-01-14 02:12:27|
|Subject: FATAL: catalog is missing 1 attribute(s) for relid 16396|
|Previous:||From: Tom Lane||Date: 2005-01-14 01:27:21|
|Subject: Re: Bug? 8.0 does not use partial index |