From: Marty Scholes <marty@outputservices.com>
To: pgsql-admin@postgresql.org
Subject: 7.4.6 pg_dump failed
Date: Wed, 26 Jan 2005 08:16:31 -0700
Message-ID: <41F7B44F.7030706@outputservices.com> (raw)
I am dumping some larger (less-used) tables from 7.4.6 to facilitate an
upgrade to 8.0.
A pg_dump of one table ran for 28:53:29.50 and produced a 30 GB dump
before it aborted with:
pg_dump: dumpClasses(): SQL command failed
pg_dump: Error message from server: out of memory for query result
pg_dump: The command was: FETCH 100 FROM _pg_dump_cursor
What causes this? This is on a Sparc box with 8GB of real memory and
104GB of virtual, so I am fairly confident that it did not run out of
memory. What would cause pg_dump to run for almost 29 hours and then
die? The table has not been accessed during that period.
To be fair, the table is not tiny, it consists of 114 segments in the
base directory: files 17935163 through 17935163.113.
The table contains a text field that could contain several hundred MB of
data, although always less than 2GB.
How can I dump this table?
Thanks,
Marty
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-admin@postgresql.org
Cc: marty@outputservices.com
Subject: Re: 7.4.6 pg_dump failed
In-Reply-To: <41F7B44F.7030706@outputservices.com>
References: <41F7B44F.7030706@outputservices.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