On Tue, 12 Oct 2004, Stef wrote:
> Pierre-Frédéric Caillaud mentioned :
> => http://www.postgresql.org/docs/7.4/static/jdbc-query.html#AEN24298
>
> My question is :
> Is this only true for postgres versions >= 7.4 ?
>
> I see the same section about "Setting fetch size to turn cursors on and of
my ho <[EMAIL PROTECTED]> writes:
> If anyone can help pls, I have a question abt the
> execution of cursor create/fetch/move , in particular
> about disk cost. When a cursor is created, is the
> whole table (with the required columns) got put into
> memory?
No. The plan is set up and then increm
Pierre-Frédéric Caillaud mentioned :
=> http://www.postgresql.org/docs/7.4/static/jdbc-query.html#AEN24298
My question is :
Is this only true for postgres versions >= 7.4 ?
I see the same section about "Setting fetch size to turn cursors on and off"
is not in the postgres 7.3.7 docs. Does this me
I just discovered this :
http://www.postgresql.org/docs/7.4/static/jdbc-query.html#AEN24298
On Tue, 12 Oct 2004 04:43:43 -0700 (PDT), my ho <[EMAIL PROTECTED]>
wrote:
Hi,
If anyone can help pls, I have a question abt the
execution of cursor create/fetch/move , in particular
about disk cost.
Hi,
If anyone can help pls, I have a question abt the
execution of cursor create/fetch/move , in particular
about disk cost. When a cursor is created, is the
whole table (with the required columns) got put into
memory? otherwise how does it work? (in term of disk
read and transfer?) after user iss
