| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | PFC <lists(at)boutiquenumerique(dot)com> |
| Cc: | aurora <aurora00(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: browsing table with 2 million records |
| Date: | 2005-10-27 01:46:14 |
| Message-ID: | 43603166.40705@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> Who needs a paginated view with 100.000 pages ?
>
> - Select min(date) and max(date) from your table
> - Present a nifty date selector to choose the records from any day,
> hour, minute, second
> - show them, with "next day" and "previous day" buttons
>
> - It's more useful to the user (most likely he wants to know what
> happened on 01/05/2005 rather than view page 2857)
> - It's faster (no more limit/offset ! just "date BETWEEN a AND b",
> indexed of course)
> - no more new items pushing old ones to the next page while you browse
> - you can pretend to your boss it's just like a paginated list
All very well and good, but now do it generically...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-10-27 03:00:13 | Re: performance on query |
| Previous Message | Christopher Kings-Lynne | 2005-10-27 01:43:24 | Re: browsing table with 2 million records |