| From: | silly8888 <silly8888(at)gmail(dot)com> |
|---|---|
| To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: cursor MOVE vs OFFSET in SELECT |
| Date: | 2009-10-26 11:14:11 |
| Message-ID: | 3c8f9f940910260414o601f6e46o644ca5e6dd8fd075@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2009/10/26 Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>:
>
>
> 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.
Well, in my experiments they always perform the same. I suspect that
the way SELECT/OFFSET is implemented is not much different than
cursor/MOVE.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2009-10-26 12:07:20 | Re: cursor MOVE vs OFFSET in SELECT |
| Previous Message | Grzegorz Jaśkiewicz | 2009-10-26 10:34:06 | Re: cursor MOVE vs OFFSET in SELECT |