<p dir="ltr">Hi,<p dir="ltr">Are all the connectors based on libpq acting the same like psql?<p dir="ltr">Peter<div
class="gmail_quote">На22.04.2015 18:57 "Andres Freund" <<a
href="mailto:andres@anarazel.de">andres@anarazel.de</a>>написа:<br type="attribution" /><blockquote
class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2015-04-22 18:49:18 +0300,
PeterSlavov wrote:<br /> > Sorry for the late answer - I got mixed up with the wrong Postgres version<br /> > and
wastetime testing on code that is not pached.<br /> > I did testing after that on the patched version and basically
Idon't see<br /> > difference when I use simple sql statement like before. Psql is putting all<br /> > in
RAM/swapbefore dumping it out ( the size is again ~15-16 GB - no change<br /> > there).<br /><br /> That's a
differentproblem though. Generally psql will, unless you<br /> configure it to use cursors, pull in the whole query in
memory.<br/><br /> I thought earlier it wasn't just psql that needed all that memory?<br /><br /> > I tried with
copy- much better memory footprint of course.<br /><br /> COPY *did* show the problem for me without the patch.<br
/><br/> > I guess I will have to forget using the SQL interface. I will try using<br /> > pg_recvlogical or some
otherway to connect my python script to the slot<br /> > using the streaming protocol .. thanks<br /><br /> That's a
goodway independently.<br /><br /> Greetings,<br /><br /> Andres Freund<br /></blockquote></div>