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

From Eric Ridge
Subject Re: Cursors and Transactions, why?
Date
Msg-id F5B488D6-8753-11D8-91AB-000A95BB5944@tcdi.com
Whole thread Raw
In response to Cursors and Transactions, why?  (Eric Ridge <ebr@tcdi.com>)
List pgsql-general
On Apr 5, 2004, at 6:44 PM, Joe Conway wrote:

> Eric Ridge wrote:
>> 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?
>
> Historically I think it was because the memory was released at the end
> of the current transaction (i.e. allocations were made in
> TopTransactionContext). But as of 7.4, cursors *can* outlive
> transactions:
> http://www.postgresql.org/docs/current/interactive/sql-declare.html
>
> WITH HOLD
> WITHOUT HOLD

holy cow!  This is fantastic.  I had no idea.  <short pause>  ooh, and
I see FETCH, in 7.4, supports absolute positioning.  Must upgrade.

thanks!

eric


pgsql-general by date:

Previous
From: "Gavin M. Roy"
Date:
Subject: Re: Storing jpgs
Next
From: Joe Conway
Date:
Subject: Re: Cursors and Transactions, why?