Re: Paged Query
От | Shaun Thomas |
---|---|
Тема | Re: Paged Query |
Дата | |
Msg-id | 4FFADB02.7010300@optionshouse.com обсуждение исходный текст |
Ответ на | Re: Paged Query (Craig Ringer <ringerc@ringerc.id.au>) |
Ответы |
Re: Paged Query
Re: Paged Query |
Список | pgsql-performance |
On 07/09/2012 07:02 AM, Craig Ringer wrote: > Do do cursors. Did you mean "Do not use cursors" here? > Then the user goes away on a week's holiday and leaves their PC at > your "next" button. This exactly. Cursors have limited functionality that isn't directly disruptive to the database in general. At the very least, the transaction ID reservation necessary to preserve a cursor long-term can wreak havoc on your transaction ID wraparound if you have a fairly busy database. I can't think of a single situation where either client caching or LIMIT/OFFSET can't supplant it with better risk levels and costs. -- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604 312-444-8534 sthomas@optionshouse.com ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
В списке pgsql-performance по дате отправления: