From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ryan Bradetich <ryan_bradetich@hp.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problem with pg_dumpall
Date: Tue, 27 Jun 2000 17:50:13 -0400
Message-ID: <14979.962142613@sss.pgh.pa.us> (raw)
In-Reply-To: <3958D5EA.82E74C68@hp.com>
References: <3958D5EA.82E74C68@hp.com>
Ryan Bradetich <ryan_bradetich@hp.com> writes:
> -- dumping out the contents of Table 'medusa'
> FATAL 1: Memory exhausted in AllocSetAlloc()
> PQendcopy: resetting connection
> SQL query to dump the contents of Table 'medusa' did not execute
> correctly. After we read all the table contents from the backend,
> PQendcopy() failed. Explanation from backend: 'FATAL 1: Memory
> exhausted in AllocSetAlloc()
> '.
> The query was: 'COPY "medusa" WITH OIDS TO stdout;
Hmm. What is the full definition of that table? (pg_dump -s -t medusa
would do.)
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, ryan_bradetich@hp.com
Subject: Re: Problem with pg_dumpall
In-Reply-To: <14979.962142613@sss.pgh.pa.us>
References: <3958D5EA.82E74C68@hp.com> <14979.962142613@sss.pgh.pa.us>
* 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