From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | CSN <cool_screen_name90001(at)yahoo(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Pagination - 1 or 2 queries? |
Date: | 2003-09-05 14:39:08 |
Message-ID: | Pine.LNX.4.33.0309050837300.30535-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 5 Sep 2003, CSN wrote:
> Since you usually need to know the total number of
> rows a query would return, do you think it's better
> to:
>
> a) Do one query with a LIMIT and OFFSET to get the
> results, and another COUNT query to get the total
> number of rows?
>
> b) Do a single query without a LIMIT and OFFSET, then
> do a seek or similiar to get at the rows you want?
>
> Most tutorials, code, etc. I've seen do "a". The
> eclipse library does "b".
Either way works. Does the eclipse library use a cursor, or grab the
whole dataset and then seek on the client side? If it uses a cursor, I'd
expect it to be the fastest and simplest implementation. Since a lot of
libs are designed to work with MySQL, they often are written in the first
method, where select count(*) is quite quick on MySQL, and MySQL doesn't
have cursor support.
With Postgresql, the cursor is likely to be the faster method.
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan Bartlett | 2003-09-05 14:39:49 | Re: Seq scan of table? |
Previous Message | Stephan Szabo | 2003-09-05 14:36:35 | Re: Optimizer picks an ineffient plan |