Isn't this a prime example of when to use a servlet or something similar
in function? It will create the cursor, maintain it, and fetch against
it for a particular page.
From: Richard Huxton [mailto:dev(at)archonet(dot)com]
Sent: Thursday, January 20, 2005 10:21 AM
To: Andrei Bintintan
Cc: pgsql-sql(at)postgresql(dot)org; pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] [SQL] OFFSET impact on Performance???
Andrei Bintintan wrote:
>> If you're using this to provide "pages" of results, could you use a
> What do you mean by that? Cursor?
> Yes I'm using this to provide "pages", but If I jump to the last pages
> it goes very slow.
DECLARE mycursor CURSOR FOR SELECT * FROM ...
FETCH FORWARD 10 IN mycursor;
Repeated FETCHes would let you step through your results. That won't
work if you have a web-app making repeated connections.
If you've got a web-application then you'll probably want to insert the
results into a cache table for later use.
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
pgsql-performance by date
|Next:||From: Bruno Almeida do Lago||Date: 2005-01-20 18:09:57|
|Subject: Re: PostgreSQL clustering VS MySQL clustering|
|Previous:||From: Ron Mayer||Date: 2005-01-20 18:03:17|
|Subject: Re: PostgreSQL vs. Oracle vs. Microsoft|
pgsql-sql by date
|Next:||From: Ragnar Hafstað||Date: 2005-01-20 19:12:06|
|Subject: Re: [SQL] OFFSET impact on Performance???|
|Previous:||From: Richard Huxton||Date: 2005-01-20 17:44:09|
|Subject: Re: ERROR: row is too big: size 9856, maximum size 8136|