Re: ResultSet storing all rows with defaulftFetchSize to 5000

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jaime Soler <jaime(dot)soler(at)gmail(dot)com>, Dave Cramer <pg(at)fastcrypt(dot)com>, Brad DeJong <bpd0018(at)gmail(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: ResultSet storing all rows with defaulftFetchSize to 5000
Date: 2018-02-12 18:50:25
Message-ID: CAB=Je-HnaV1cEHZfdtTrV=QjYc-F47rbhsOo5PQowPao4DiXxQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Tom Lane 2018-02-12 18:57:50 Re: ResultSet storing all rows with defaulftFetchSize to 5000
Previous Message Tom Lane 2018-02-12 16:39:08 Re: ResultSet storing all rows with defaulftFetchSize to 5000