From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mike Charnoky <noky(at)nextbus(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_restore and large files |
Date: | 2004-02-05 15:33:58 |
Message-ID: | 2914.1075995238@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Mike Charnoky <noky(at)nextbus(dot)com> writes:
> I am currently using PostgreSQL v7.3.4 on a RedHat 8.0 system (2.4.23 kernel)
> using the ext3 filesystem. I am experiencing problems when performing a
> pg_restore using a file which is 2.3G in size. The dump, which seemed to run
> smoothly, was created using the -Fc option. When I perform the restore, the
> following error occurs before the pg_restore fails:
> pg_restore: [custom archiver] error during file seek: Invalid argument
> pg_restore: *** aborted because of error
> Why is this happening? The error comes from pg_backup_custom.c, it seems that
> an fseeko() is failing (even though this is the way to support large
> files).
Hm, can you insert some debugging printout to show the offset value
being passed to fseeko? That would let us eliminate one of pg_restore
and the kernel as being at fault. Another thing that'd be useful is to
run pg_restore under gdb with a breakpoint set at die_horribly, so that
you could get a stack trace from the point of the failure.
I am suspicious that it's a pg_restore bug and the problem has to do
with manipulating file offsets as plain integers someplace. Not enough
info yet to go searching, though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Lebedev | 2004-02-05 15:34:27 | Re: dblink: rollback transaction |
Previous Message | Carlos Ojea Castro | 2004-02-05 15:24:04 | : Proper tool to display graphics? |