| From: | Alex Goncharov <alex-goncharov(at)comcast(dot)net> |
|---|---|
| To: | Abhijit Menon-Sen <ams(at)toroid(dot)org>, Yeb Havinga <yebhavinga(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: libpq, PQexecPrepared, data size sent to FE vs. FETCH_COUNT |
| Date: | 2010-05-25 13:17:06 |
| Message-ID: | E1OGu0I-000FOv-7b@daland.home |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
,--- Abhijit Menon-Sen (Tue, 25 May 2010 17:26:18 +0530) ----*
| Unless you explicitly declare and fetch from an SQL-level cursor, your
| many GBs of data are going to be transmitted to libpq, which will eat
| lots of memory. (The wire protocol does have something like cursors,
| but libpq does not use them, it retrieves the entire result set.)
,--- Yeb Havinga (Tue, 25 May 2010 14:08:51 +0200) ----*
| The GBs of data are gathered at the site of the libpq client (pgresult
| object gathered/allocated while consuming result input from backend).
`------------------------------------------------------*
Thank you very much!
-- Alex -- alex-goncharov(at)comcast(dot)net --
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Chernow | 2010-05-25 13:20:55 | Re: libpq, PQexecPrepared, data size sent to FE vs. FETCH_COUNT |
| Previous Message | Stephen Frost | 2010-05-25 12:44:20 | Re: ExecutorCheckPerms() hook |