| From: | "Abraham, Danny" <danny_abraham(at)bmc(dot)com> |
|---|---|
| To: | <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Sliding windows on LIBPQ |
| Date: | 2007-11-28 14:43:00 |
| Message-ID: | E9DE7963E5EA6546B42A979EC28B4D01368A8D8B@hou-ex-02.adprod.bmc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Is there a way to break the PGresult array to chuncks Like Oracle?
I mean, without changing the text of given queries, can we somehow
limit the memory consumption of a client that is using LIBPQ?
The API is ...
extern PGresult *PQexec(PGconn *conn, const char *query);
Is there any "SLiding Window" layer that breaks the PGresult into
chuncks?
Big queries take a lot more memory on the client side compared to other
DB clients.
Thanks
Danny
Danny Abraham
BMC Software
CTM&D Business Unit
972-52-4286-513
danny_abraham(at)bmc(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | andrew klassen | 2007-11-28 22:40:06 | postmaster process and multithreading |
| Previous Message | Tom Lane | 2007-11-27 02:24:33 | Re: v8.1: Error severity on libpq PGconn* |