Did the dump come from those machines? If so, it is probably not a valid archive anyway because you hit the 2gig limit. My suggestion would be to recompile PostgreSQL with the 64bit file access.Advertising
Sincerely,
Joshua D. Drake
Kurt Roeckx wrote:
On Sun, Nov 23, 2003 at 10:51:10PM -0500, Anjan Dave wrote:
Hi All:
I am trying to restore a database on a different machine (7.2.3 on Sol9 to 7.2.4 RH8), and i get the following error, that i haven't seen before:
-bash-2.05b$ pg_restore -d access -Ft -a access.dump.tar pg_restore: [tar archiver] could not open TOC file for input: File too large Segmentation fault -bash-2.05b$
-bash-2.05b$ ls -l
total 2339148
-rw-r--r-- 1 root root 2323785216 Nov 23 22:43 access.dump.tar
The problem is that your file is over 2 GB, your OS/libc has a problem opening such big files (using fopen()).
Try cat access.dump.tar | pg_restore -d access -Ft -a
I read somewhere that there's a patch for this: http://dbforums.com/arch/173/2003/1/675653
Will this patch fix it? Where do i get it from and how do i apply it?
The patch only fixed that "segmentation fault", not the "File too large".
Kurt
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
-- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
