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 DB061D1B380 for ; Mon, 19 Jul 2004 17:06:48 -0300 (ADT) 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 65346-06 for ; Mon, 19 Jul 2004 20:06:44 +0000 (GMT) Received: from mpls-qmqp-04.inet.qwest.net (mpls-qmqp-04.inet.qwest.net [63.231.195.115]) by svr1.postgresql.org (Postfix) with SMTP id A7247D1B375 for ; Mon, 19 Jul 2004 17:06:42 -0300 (ADT) Received: (qmail 36640 invoked by uid 0); 19 Jul 2004 20:06:44 -0000 Received: from mpls-pop-12.inet.qwest.net (63.231.195.12) by mpls-qmqp-04.inet.qwest.net with QMQP; 19 Jul 2004 20:06:44 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-12.inet.qwest.net with SMTP; 19 Jul 2004 20:06:44 -0000 Date: Mon, 19 Jul 2004 14:07:54 -0600 Message-Id: <1090267674.709.5.camel@localhost.localdomain> From: "Scott Marlowe" To: "Kris Kiger" Cc: pgsql-admin@postgresql.org Subject: Re: Large file support needed? Trying to identify root of In-Reply-To: <40FC20F0.1000402@musicrebellion.com> References: <40F6A366.5040701@musicrebellion.com> <40F6B86B.3020400@spacemonkeylabs.com> <40F6DC6F.4000707@musicrebellion.com> <40FC20F0.1000402@musicrebellion.com> Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200407/221 X-Sequence-Number: 14289 On Mon, 2004-07-19 at 13:28, Kris Kiger wrote: > I've got a database that is a single table with 5 integers, a timestamp > with time zone, and a boolean. The table is 170 million rows in length. > The contents of the tar'd dump file it produced using: > pg_dump -U postgres -Ft test > test_backup.tar > is: 8.dat (approximately 8GB), a toc, and restore.sql. > > No errors are reported on dump, however, when a restore is attempted I get: > > ERROR: unexpected message type 0x58 during COPY from stdin > CONTEXT: COPY test_table, line 86077128: "" > ERROR: could not send data to client: Broken pipe > CONTEXT: COPY test_table, line 86077128: "" > > I am doing the dump & restore on the same machine. > > Any ideas? If the file is too large, is there anyway postgres could > break it up into smaller chunks for the tar when backing up? Thanks for > the help! How, exactly, are you restoring? Doing things like: cat file|pg_restore ... can cause problems because cat is often limited to 2 gigs on many OSes. Just use a redirect: psql dbname