From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Lorenz <mlorenz1@hotmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Query slows after offset of 100K
Date: Thu, 14 Feb 2008 16:55:03 -0500
Message-ID: <19472.1203026103@sss.pgh.pa.us> (raw)
In-Reply-To: <BAY111-W375B12EB37C7EF3BE82BE793250@phx.gbl>
References: <BAY111-W56DE7AD29405FE5C2BF1A93250@phx.gbl>
<17159.1203016095@sss.pgh.pa.us>
<BAY111-W375B12EB37C7EF3BE82BE793250@phx.gbl>
Michael Lorenz <mlorenz1@hotmail.com> writes:
> Fair enough, and I did think of this as well. However, I didn't think this was a viable option in my case, since we're currently allowing the user to randomly access the pages (so $lastkey wouldn't really have any meaning). The user can choose to sort on object ID, name or modification time, and then go straight to any page in the list. With 750K records, that's around 37K pages.
Well, my first question is whether that user interface is actually
useful to anyone. If you have a dictionary and you want to look up
"foosball", do you start by guessing that it's on page 432? No, you
look for the "F" tab. I'd suggest that what you want is to present
links that let people go to specific spots in the key distribution,
rather than expressing it in terms of so-many-pages.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, mlorenz1@hotmail.com
Subject: Re: Query slows after offset of 100K
In-Reply-To: <19472.1203026103@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox