Re: cursor MOVE vs OFFSET in SELECT

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: silly8888 <silly8888(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: cursor MOVE vs OFFSET in SELECT
Date: 2009-10-26 10:34:06
Message-ID: 2f4958ff0910260334r2bec490cq6f0181fb317fdc36@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Oct 26, 2009 at 10:30 AM, silly8888 <silly8888(at)gmail(dot)com> wrote:

> Suppose that you have a query, say $sql_query, which is very
> complicated and produces many rows. Which of the following is going to
> be faser:
>
> $sql_query OFFSET 3000 LIMIT 12;
>
> or
>
> BEGIN;
> DECLARE cur1 CURSOR FOR $sql_query;
> MOVE 3000 IN cur1;
> FETCH 12 FROM cur1;
> COMMIT;
>
> Naturally, the former cannot be slower than the latter. So my question
> essentially is whether the MOVE operation on a cursor is
> (significantly) slower that a OFFSET on the SELECT.
>

OFFSET/LIMIT. Afaik cursor always fetches everything.

--
GJ

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message silly8888 2009-10-26 11:14:11 Re: cursor MOVE vs OFFSET in SELECT
Previous Message silly8888 2009-10-26 10:30:50 cursor MOVE vs OFFSET in SELECT