Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f93HjCn61165 for ; Wed, 3 Oct 2001 13:45:12 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f93HfYI06312; Wed, 3 Oct 2001 13:41:35 -0400 (EDT) To: "Darko Prenosil" cc: "Bruce Momjian" , "pgsql interfaces" Subject: Re: In-reply-to: <007e01c14c2e$d1e69240$ef00000a@darko> References: <007e01c14c2e$d1e69240$ef00000a@darko> Comments: In-reply-to "Darko Prenosil" message dated "Wed, 03 Oct 2001 19:13:07 +0200" Date: Wed, 03 Oct 2001 13:41:34 -0400 Message-ID: <6309.1002130894@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/9 X-Sequence-Number: 1977 "Darko Prenosil" writes: > We wanted to use non-blocking PQSendQuery to send a large query which = > consists of many SELECTs. Our pglib interface sent just first 8192 bytes = > and returned EOF. Whole query was more than 64k. I've said since day one that libpq's non-blocking mode is fundamentally broken --- see http://fts.postgresql.org/db/mw/msg.html?mid=35774 and rest of that thread. Tempt me not too far, or I'll rip it all out until someone reimplements it in a non-broken fashion ... regards, tom lane