You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2019. It is now read-only.
Sorry if ignorant here. Since cursors open a transaction, I assume it will be left to the query planner to determine the best way to execute.
Just wondering about the server performance impact of doing a large cursor query with some joins. It should make an initial up-front temporary table if the result is large enough, then stream from that temp result set, right? It's not going to re-open a new transaction every time?
that is, is this a client-side only cursor, or does it issue a server-side cursor as well?