| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
| Cc: | Gregg Jaskiewicz <gryzman(at)gmail(dot)com>, Misa Simic <misa(dot)simic(at)gmail(dot)com>, Hermann Matthes <hermann(dot)matthes(at)web(dot)de>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Paged Query |
| Date: | 2012-07-09 13:22:10 |
| Message-ID: | 4FFADB02.7010300@optionshouse.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig James | 2012-07-09 14:16:00 | Re: Paged Query |
| Previous Message | Craig Ringer | 2012-07-09 12:02:38 | Re: Paged Query |