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 BA00232A271 for ; Mon, 18 Oct 2004 16:55:27 +0100 (BST) 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 23827-07 for ; Mon, 18 Oct 2004 15:55:21 +0000 (GMT) Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by svr1.postgresql.org (Postfix) with ESMTP id 5709332A178 for ; Mon, 18 Oct 2004 16:55:21 +0100 (BST) Received: from [192.168.1.20] (clbb-248.saw.net [64.146.135.248]) (authenticated) by hosting.commandprompt.com (8.11.6/8.11.6) with ESMTP id i9IFtIt03334; Mon, 18 Oct 2004 08:55:18 -0700 Message-ID: <4173E6F1.8060003@commandprompt.com> Date: Mon, 18 Oct 2004 08:53:21 -0700 From: "Joshua D. Drake" Organization: Command Prompt, Inc. User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Fowler Cc: pgsql-admin list Subject: Re: large dumps won't restore References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; 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: 200410/215 X-Sequence-Number: 15208 > When using pg_dump + psql: > > I get a similar error. In one table that has about 5.4 million rows, > the dump has several incomplete rows in the large block of copy data. > It seems to attempt to fill the copy with data from the *next* line. > > ERROR: invalid input syntax for type timestamp: "4" > CONTEXT: COPY foo_data, line 169371, column mod_date: "4" > > going to 169371 lines after the start of the copy, indeed there is a > short > row (by two), and two fields in on the *next* line is indeed a "4" > > > Both seem to have the same problem - incomplete COPY row data. any ideas? > Well you aren't going to like this but I see two solutions: 1. Cut out the rows listed and reimport after the copy completes. 2. Perform the pg_dump as inserts which will make the restore very slow but should complete correctly. Is the dump and restore happening on the same platform? Sincerely, Joshua D. Drake > > > [ \ / > [ >X< Christian Fowler | spider@viovio.com > [ / \ http://www.viovio.com | http://www.tikipro.org > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL