From: | Pierre-Frédéric Caillaud <lists(at)boutiquenumerique(dot)com> |
---|---|
To: | "my ho" <mthoatbanjo(at)yahoo(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: execute cursor fetch |
Date: | 2004-10-12 12:36:10 |
Message-ID: | opsfrbykrycq72hf@musicbox |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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 <mthoatbanjo(at)yahoo(dot)com>
wrote:
> 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 issues command
> move/fetch, how does postgre speed up the query in
> compare to normal selection?
> Thanks a lot,
> regards,
> MT Ho
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail Address AutoComplete - You start. We finish.
> http://promotions.yahoo.com/new_mail
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Stef | 2004-10-12 13:05:15 | Re: execute cursor fetch |
Previous Message | Aaron Werman | 2004-10-12 12:20:52 | Re: Normal case or bad query plan? |