X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8292A3A5C1B for ; Wed, 26 Jan 2005 15:16:39 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 30192-05 for ; Wed, 26 Jan 2005 15:16:28 +0000 (GMT) Received: from outputservices.com (outputt1130.customer.frii.net [216.17.159.130]) by svr1.postgresql.org (Postfix) with ESMTP id 193F13A5C32 for ; Wed, 26 Jan 2005 15:16:30 +0000 (GMT) Received: from outputservices.com (outputservices.com [137.106.76.15]) by outputservices.com (8.10.2+Sun/8.11.3) with ESMTP id j0QFGWJ05255 for ; Wed, 26 Jan 2005 08:16:32 -0700 (MST) Message-ID: <41F7B44F.7030706@outputservices.com> Date: Wed, 26 Jan 2005 08:16:31 -0700 From: Marty Scholes User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.9) Gecko/20020517 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: 7.4.6 pg_dump failed Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/269 X-Sequence-Number: 16128 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