Cursors and Transactions, why? - Mailing list pgsql-general

From Eric Ridge
Subject Cursors and Transactions, why?
Date
Msg-id CF4BA056-8743-11D8-91AB-000A95BB5944@tcdi.com
Whole thread Raw
Responses Re: Cursors and Transactions, why?
Re: Cursors and Transactions, why?
List pgsql-general
Why must a cursor be defined in an open transaction?  Obviously there's
a good reason, but I can't figure it out.  On a high level, what would
be involved in allowing a cursor to outlive the transaction that
created it?

Cursors seem as if they have some nice performance benefits (esp. if
you're not using all rows found), but their usefulness drops
considerably since you must leave a transaction open.

eric


pgsql-general by date:

Previous
From: Manfred Koizar
Date:
Subject: Re: Large DB
Next
From: William White
Date:
Subject: left and overleft/notright revisited: why !>> and !<< might be poor names