unordained wrote:

>
> I don't typically deal with cursors explicitly, but that's probably what this boils down to. If a
> client application connects to the database, starts a transaction, issues a SELECT statement and
> starts to fetch results from it ("iterating" -- pulling more rows until there are none left), sets
> a savepoint so it can safely do (and undo) some work based on the data it's pulling from that
> initial SELECT statement, and at some point along the way a rollback-to-savepoint is issued, will
> the client still be able to continue pulling rows from that initial SELECT, or will the act of
> issuing a rollback-to-savepoint cause it (the cursor?) to no longer be available?

Rollback to a savepoint doesn't affect open cursors, unless the cursor
is based on uncommitted changes within the same transaction (and under
the given savepoint).


Dmitry