Abhijit Menon-Sen <a...@toroid.org> wrote: > 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.)
Sounds like a project. Anyone got any suggestions about semantics and function names? (Assuming that this can be done without causing more problems on the backend; I'd rather one frontend client get messed up than mess up the server if someone makes a query like that.) I'm not exactly volunteering to work on something like this (my TODO list is a trifle long) but I'm working on a native Go language interface for PostgreSQL presently (influced by but not an exact clone of libpq) so it's perhaps something I could do if I get free time in future. Giles -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
