Re: BUG #14411: Issue with using OFFSET
| От | Kevin Grittner |
|---|---|
| Тема | Re: BUG #14411: Issue with using OFFSET |
| Дата | |
| Msg-id | CACjxUsMPONtsFR2VZgseugBOTvvQpo=7aKRap=VfRviZG8yVJg@mail.gmail.com обсуждение исходный текст |
| Ответ на | BUG #14411: Issue with using OFFSET (jkoceniak@mediamath.com) |
| Ответы |
Re: BUG #14411: Issue with using OFFSET
|
| Список | pgsql-bugs |
On Thu, Nov 3, 2016 at 3:29 PM, <jkoceniak@mediamath.com> wrote: > Query performance decreases as the OFFSET increases. Not a bug, but a fact of life. It must generate the OFFSET number of rows and continue to generated the next LIMIT rows (or continue processing until there are no rows). If matching rows are scarce after OFFSET rows are found, it can take a while to get enough or to find out that LIMIT rows don't exist. Personally, I never use OFFSET and LIMIT for pagination; there are better ways for most situations. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-bugs по дате отправления: