Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id BBCCA2E005A for ; Sun, 6 Apr 2008 21:08:17 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 87590-02 for ; Sun, 6 Apr 2008 21:08:07 -0300 (ADT) X-Greylist: delayed 00:09:13.241462 by SQLgrey-1.7.5 Received: from ambcs03.stccmop.org (amb1200.ccalmr.ogi.edu [129.95.72.13]) by developer.postgresql.org (Postfix) with ESMTP id E0EFD2E0056 for ; Sun, 6 Apr 2008 21:08:14 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by ambcs03.stccmop.org (Postfix) with ESMTP id 64EC7C0C2D2 for ; Sun, 6 Apr 2008 16:58:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at Received: from ambcs03.stccmop.org ([127.0.0.1]) by localhost (ambcs03.stccmop.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4VF879q2IPwe for ; Sun, 6 Apr 2008 16:58:58 -0700 (PDT) Received: from [129.95.72.50] (amb18.ccalmr.ogi.edu [129.95.72.50]) by ambcs03.stccmop.org (Postfix) with ESMTP id EBF48C0C2D0 for ; Sun, 6 Apr 2008 16:58:58 -0700 (PDT) Message-ID: <47F963C1.7070100@stccmop.org> Date: Sun, 06 Apr 2008 16:58:57 -0700 From: Charles Seaton User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: libpq query length limit Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.082 tagged_above=0 required=5 tests=AWL=0.082 X-Spam-Level: X-Archive-Number: 200804/3 X-Sequence-Number: 6714 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. Is there a limit on the length of a query, and is there a way around this? thanks, Charles Seaton