From: Ed Loehr <eloehr@austin.rr.com>
To: Graham Vickrage <graham@digitalplanit.com>
Cc: pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: pg_dump problem
Date: Mon, 26 Jun 2000 12:50:36 -0500
Message-ID: <395797EC.C9A1F010@austin.rr.com> (raw)
References: <NDBBJABDILOPAOOMFJHOKENDCCAA.graham@digitalplanit.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: eloehr@austin.rr.com, graham@digitalplanit.com
Subject: Re: pg_dump problem
In-Reply-To: <395797EC.C9A1F010@austin.rr.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox