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

From Joe Conway
Subject Re: Cursors and Transactions, why?
Date
Msg-id 407386FF.9020802@joeconway.com
Whole thread Raw
In response to Re: Cursors and Transactions, why?  (Eric Ridge <ebr@tcdi.com>)
Responses Re: Cursors and Transactions, why?
List pgsql-general
Eric Ridge wrote:
> On Apr 6, 2004, at 11:54 AM, Jan Wieck wrote:
>> And now you know why they are so good if you don't use all rows. This
>> benefit I think goes away if you use Joe Conway's suggestion of WITH
>> HOLD.
>
> Okay, so WITH HOLD is actually materializing the entire resultset
> (sequential scan or otherwise)?  If that's true, you're right, some of
> the benefits do go away.

Keep in mind that the tuplestore stays in memory as long as it fits
within sort_mem kilobytes. And you can do:

   set sort_mem to <some_large_number>;

prior to COMMIT, and then

   set sort_mem to default;

after COMMIT, as long as you can afford the memory use. A bit ugly, but
it might come in handy ;-)

Joe

pgsql-general by date:

Previous
From: "Rajat Katyal"
Date:
Subject: Re: PERFORM statement inside procedure
Next
From: Bruce Momjian
Date:
Subject: Re: thread_test.c problems