Re: ResultSet storing all rows with defaulftFetchSize to 5000 - Mailing list pgsql-jdbc

From Vladimir Sitnikov
Subject Re: ResultSet storing all rows with defaulftFetchSize to 5000
Date
Msg-id CAB=Je-HnaV1cEHZfdtTrV=QjYc-F47rbhsOo5PQowPao4DiXxQ@mail.gmail.com
Whole thread Raw
In response to Re: ResultSet storing all rows with defaulftFetchSize to 5000  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ResultSet storing all rows with defaulftFetchSize to 5000  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-jdbc
Tom>It's available through DECLARE CURSOR WITH HOLD.

docs>In the current implementation, the rows represented by a held cursor are copied into a temporary file or memory area so that they remain available for subsequent transactions.

The backend materializes, so it is a sad thing.
Is there a change "with hold" can be implemented without materialization?
I just wonder if it is more like "not yet implemented" or if it would take incredible amount of resources to implement.

Vladimir

pgsql-jdbc by date:

Previous
From: Tom Lane
Date:
Subject: Re: ResultSet storing all rows with defaulftFetchSize to 5000
Next
From: Tom Lane
Date:
Subject: Re: ResultSet storing all rows with defaulftFetchSize to 5000