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 17F26D1B375 for ; Mon, 19 Jul 2004 16:29:36 -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 48330-01 for ; Mon, 19 Jul 2004 19:29:31 +0000 (GMT) Received: from stamp.musicrebellion.com (unknown [209.120.177.10]) by svr1.postgresql.org (Postfix) with ESMTP id 1A2BDD1B2E0 for ; Mon, 19 Jul 2004 16:29:25 -0300 (ADT) Received: from dsl093-203-229.ind1.dsl.speakeasy.net ([66.93.203.229] helo=musicrebellion.com) by stamp.musicrebellion.com with asmtp (Exim 4.30 #2 (Debian)) id 1Bmdp9-0004ra-F1 for ; Mon, 19 Jul 2004 14:29:19 -0500 Message-ID: <40FC20F0.1000402@musicrebellion.com> Date: Mon, 19 Jul 2004 14:28:48 -0500 From: Kris Kiger User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 X-Accept-Language: en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Large file support needed? Trying to identify root of error. References: <40F6A366.5040701@musicrebellion.com> <40F6B86B.3020400@spacemonkeylabs.com> <40F6DC6F.4000707@musicrebellion.com> 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.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/218 X-Sequence-Number: 14286 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! Kris