From: | Ragnar Hafstað <gnari(at)simnet(dot)is> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Cc: | Andrei Bintintan <klodoma(at)ar-sd(dot)net>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [SQL] OFFSET impact on Performance??? |
Date: | 2005-01-20 19:23:12 |
Message-ID: | 1106248992.22416.25.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance pgsql-sql |
On Thu, 2005-01-20 at 19:12 +0000, Ragnar Hafstað wrote:
> On Thu, 2005-01-20 at 11:59 -0500, Greg Stark wrote:
>
> > The best way to do pages for is not to use offset or cursors but to use an
> > index. This only works if you can enumerate all the sort orders the
> > application might be using and can have an index on each of them.
> >
> > To do this the query would look something like:
> >
> > SELECT * FROM tab WHERE col > ? ORDER BY col LIMIT 50
> >
> > Then you take note of the last value used on a given page and if the user
> > selects "next" you pass that as the starting point for the next page.
>
> this will only work unchanged if the index is unique. imagine , for
> example if you have more than 50 rows with the same value of col.
>
> one way to fix this is to use ORDER BY col,oid
and a slightly more complex WHERE clause as well, of course
gnari
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2005-01-20 19:29:34 | Re: [SQL] OFFSET impact on Performance??? |
Previous Message | Steve Wampler | 2005-01-20 19:13:17 | Re: PostgreSQL clustering VS MySQL clustering |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-01-20 20:38:07 | Re: ERROR: row is too big: size 9856, maximum size 8136 |
Previous Message | Ragnar Hafstað | 2005-01-20 19:12:06 | Re: [SQL] OFFSET impact on Performance??? |