Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id C2E802E0046 for ; Tue, 8 Apr 2008 11:50:33 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 35936-01 for ; Tue, 8 Apr 2008 11:50:29 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id 8A6372E0045 for ; Tue, 8 Apr 2008 11:50:29 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m38EoR6I001112; Tue, 8 Apr 2008 10:50:27 -0400 (EDT) To: Charles Seaton cc: pgsql-interfaces@postgresql.org Subject: Re: libpq query length limit In-reply-to: <47F963C1.7070100@stccmop.org> References: <47F963C1.7070100@stccmop.org> Comments: In-reply-to Charles Seaton message dated "Sun, 06 Apr 2008 16:58:57 -0700" Date: Tue, 08 Apr 2008 10:50:27 -0400 Message-ID: <1111.1207666227@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/4 X-Sequence-Number: 6715 Charles Seaton writes: > I am using libpq to access a PostgreSQL 8.2.7 database. > I am encountering segfault errors when the query length exceeds some > value greater than 633 characters and less than 2492 characters. The > database log shows the message > LOG: 08P01: unexpected EOF on client connection > The query that causes problems through libpq can be run directly in psql > without a problem. Almost certainly, this is a bug within the code calling libpq, and not in libpq itself. Many people routinely use queries much longer than that ... regards, tom lane