From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Alex Goncharov <alex-goncharov(at)comcast(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: libpq, PQexecPrepared, data size sent to FE vs. FETCH_COUNT |
Date: | 2010-05-25 14:47:42 |
Message-ID: | 4BFBE30E.6070305@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alex Goncharov wrote:
> ,--- I/Alex (Mon, 24 May 2010 12:25:18 -0400) ----*
> | No equivalent of FETCH_COUNT is available at the libpq level, so I
> | assume that the interface I am using is smart enough not to send
> | gigabytes of data to FE.
> |
> | Where does the result set (GBs of data) reside after I call
> | PQexecPrepared? On BE, I hope?
>
> Sorry for asking again...
>
> No sarcasm meant: is there no straightforward answer here? Or nobody
> is certain? Or a wrong list?
>
>
>
You have been given the answer. Please re-read the replies, e.g. the one
from Abhijit Menon-Sen.
The data is saved on the client side before the call returns. If that
uses too much memory, use a cursor.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Adams | 2010-05-25 14:52:30 | Re: JSON manipulation functions |
Previous Message | Mike Fowler | 2010-05-25 14:31:08 | [PATCH] Add XMLEXISTS function from the SQL/XML standard (was: Add xpath_exists Function) |