Skip site navigation (1) Skip section navigation (2)

Top-k optimizations?

From: David Fetter <david(at)fetter(dot)org>
To: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Top-k optimizations?
Date: 2005-01-14 01:43:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

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
from this.

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
in PostgreSQL?

Hoping this stimulates some friendly & informative discussion... :)

David Fetter david(at)fetter(dot)org
phone: +1 510 893 6100   mobile: +1 415 235 3778

Remember to vote!


pgsql-hackers by date

Next:From: Marc G. FournierDate: 2005-01-14 02:12:27
Subject: FATAL: catalog is missing 1 attribute(s) for relid 16396
Previous:From: Tom LaneDate: 2005-01-14 01:27:21
Subject: Re: Bug? 8.0 does not use partial index

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group