Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55])
	by hub.org (8.10.1/8.10.1) with ESMTP id e5QHk5125776
	for <pgsql-sql@postgresql.org>; Mon, 26 Jun 2000 13:46:05 -0400 (EDT)
Received: from austin.rr.com ([24.93.36.87]) by Mail.austin.rr.com with
	Microsoft SMTPSVC(5.5.1877.357.35); Mon, 26 Jun 2000 12:45:41 -0500
Message-ID: <395797EC.C9A1F010@austin.rr.com>
Date: Mon, 26 Jun 2000 12:50:36 -0500
From: Ed Loehr <eloehr@austin.rr.com>
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20smp i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Graham Vickrage <graham@digitalplanit.com>
CC: pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: pg_dump problem
References: <NDBBJABDILOPAOOMFJHOKENDCCAA.graham@digitalplanit.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200006/230

Graham Vickrage wrote:
> 
> I am trying to backup a production database running on v6.5 and restore it
> on our test machine running v6.5.
> 
> The largest table has about 750,000 rows, the other 5 tables are very small
> approx 100 rows.
> 
> When I try to restore the database using  "psql -e database < db.out" I get
> the error message
> "query buffer max length of 16384 exceeded" after each row.
> 
> Would somebody please tell me how to increse this buffer (assuming this is
> whats required to solve the problem) as I have looked though the
> documentation and I am still struggling :-(

You probably don't need to increase the buffer.  More likely, there is an
unterminated string constant somewhere in db.out.  Yes, that would
probably be a bug in pg_dump, but I do vaguely recall problems in 6.5*
with pg_dump.  You might search deja for your error message.

Regards,
Ed Loehr