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 E90A7D1B587 for ; Tue, 8 Jun 2004 22:41:06 -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 94316-09 for ; Wed, 9 Jun 2004 01:41:06 +0000 (GMT) Received: from ptb-relay02.plus.net (ptb-relay02.plus.net [212.159.14.213]) by svr1.postgresql.org (Postfix) with ESMTP id 782A3D1B497 for ; Tue, 8 Jun 2004 22:41:00 -0300 (ADT) Received: from [212.159.87.229] (helo=thelabyrinth.force9.co.uk) by ptb-relay02.plus.net with esmtp (Exim) id 1BXs5P-000MGZ-Jd; Wed, 09 Jun 2004 01:41:03 +0000 Received: from ruth.localdomain (ruth.localdomain [192.168.0.1]) by thelabyrinth.force9.co.uk (Postfix) with ESMTP id D3C7E30081; Wed, 9 Jun 2004 01:41:46 +0100 (BST) Date: Wed, 9 Jun 2004 02:42:07 +0100 (BST) From: Sam Barnett-Cormack X-X-Sender: sdb@localhost.localdomain To: Kris Kiger Cc: pgsql-admin@postgresql.org Subject: Re: Upper limit for a dump file? In-Reply-To: <40C630E0.6080901@musicrebellion.com> Message-ID: References: <40C630E0.6080901@musicrebellion.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: 200406/98 X-Sequence-Number: 13758 On Tue, 8 Jun 2004, Kris Kiger wrote: > I am trying to restore a dump of two independant databases. Each > database is the same in table structure (there is only one table that > consists of 5 integers, a timestamp with time zone, and a boolean). > Here are the number of rows: > DB1 - 115,539,855 rows > DB2 - 118,022,948 rows > > There are no keys/indexes/etc on the table. The uncompressed tar file > is 5.5GB. I am running PG 7.4. > > When I try to move this data to another database (via pg_dump & > pg_restore) it fails each time, for each database) with: > pg_restore: [archiver (db)] error returned by PQputline > > I find it highly unlikely that I have corrupted data in each database, > since each were generated on different postgres installations on > different machines. I can still query the original databases (DB1 & > DB2) with no problem. It looks like all of the data is intact. Any > ideas what may be the root of the problem or how I can find out more > about this error PQputline returned? Perhaps the other machine has a filesystem limit forbidding such large files? Various filesystems have historically been limited to 2GB -- Sam Barnett-Cormack Software Developer | Student of Physics & Maths UK Mirror Service (http://www.mirror.ac.uk) | Lancaster University