| From: | Віталій Тимчишин <tivv00(at)gmail(dot)com> |
|---|---|
| To: | Misa Simic <misa(dot)simic(at)gmail(dot)com> |
| Cc: | Gregg Jaskiewicz <gryzman(at)gmail(dot)com>, Hermann Matthes <hermann(dot)matthes(at)web(dot)de>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Paged Query |
| Date: | 2012-07-11 08:23:01 |
| Message-ID: | CABWW-d22e7gv=JoQKsNzdZ2TbEYn4HL-v1TN1ks=+Si=vaQW6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Понеділок, 9 липня 2012 р. користувач Misa Simic <misa(dot)simic(at)gmail(dot)com>
написав:
>
>
> 2012/7/9 Gregg Jaskiewicz <gryzman(at)gmail(dot)com>
>>
>> Use cursors.
>> By far the most flexible. offset/limit have their down sides.
>
>
> Well, I am not aware what down sides there are in LIMIT OFFSET what does
not exist in any other solutions for paged queries...
'where key > last-value order by key limit N' is much better in performance
for large offsets.
p.s. Sorry for previous email- hit send too early.
--
Best regards,
Vitalii Tymchyshyn
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2012-07-11 08:23:07 | Re: how could select id=xx so slow? |
| Previous Message | Віталій Тимчишин | 2012-07-11 08:15:38 | Re: Paged Query |