pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedDB restore fails W2k.
2+ messages / 2 participants
[nested] [flat]
* DB restore fails W2k.
@ 2005-08-21 21:16 Dan <danilos@home.se>
0 siblings, 1 reply; 2+ messages in thread
From: Dan @ 2005-08-21 21:16 UTC (permalink / raw)
To: pgsql-admin
Hello,
We have upgraded our PostgreSQL database version from 7.3.1 (Cygwin) under
Windows 2000 server to v8.03 for windows.
Now we dumped our database (app. size 6 GB) with PgAdmin III with success.
The problem now is that we can't completely restore our database with the
dump file. The restore utility just stops when reaching a certain point in
the dump file.
Please help us, we can't afford loosing our database with several years of
work.
Thanks in advance.
/Dan
Here is some info on the dump file:
; Archive created at Wed Aug 17 21:09:56 2005
; dbname: a_db
; TOC Entries: 43
; Compression: -1
; Dump Version: 1.10-0
; Format: CUSTOM
; Integer: 4 bytes
; Offset: 4 bytes
; Dumped from database version: 7.3.1
; Dumped by pg_dump version: 8.0.0
Error displayed when restoring.
C:\Program Files\PostgreSQL\8.0\pgAdmin III\pg_restore.exe -i -h localhost
-p 5432 -U postgres -d a_db -a -t pictures -v "D:\a_db.backup"
pg_restore: connecting to database for restore
pg_restore: restoring data for table " pictures"
pg_restore: [custom archiver] error during file seek: Invalid argument
pg_restore: *** aborted because of error
Process returned exit code 1.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: DB restore fails W2k.
@ 2005-08-30 18:11 Scott Marlowe <smarlowe@g2switchworks.com>
parent: Dan <danilos@home.se>
0 siblings, 0 replies; 2+ messages in thread
From: Scott Marlowe @ 2005-08-30 18:11 UTC (permalink / raw)
To: Dan <danilos@home.se>; +Cc: pgsql-admin
On Sun, 2005-08-21 at 16:16, Dan wrote:
> Hello,
>
>
>
> We have upgraded our PostgreSQL database version from 7.3.1 (Cygwin)
> under Windows 2000 server to v8.03 for windows.
>
>
>
> Now we dumped our database (app. size 6 GB) with PgAdmin III with
> success. The problem now is that we can’t completely restore our
> database with the dump file. The restore utility just stops when
> reaching a certain point in the dump file.
>
> Please help us, we can’t afford loosing our database with several
> years of work.
>
> Thanks in advance.
>
>
>
> /Dan
>
>
>
> Here is some info on the dump file:
>
> ; Archive created at Wed Aug 17 21:09:56 2005
>
> ; dbname: a_db
>
> ; TOC Entries: 43
>
> ; Compression: -1
>
> ; Dump Version: 1.10-0
>
> ; Format: CUSTOM
>
> ; Integer: 4 bytes
>
> ; Offset: 4 bytes
>
> ; Dumped from database version: 7.3.1
>
> ; Dumped by pg_dump version: 8.0.0
>
>
>
> Error displayed when restoring.
>
> C:\Program Files\PostgreSQL\8.0\pgAdmin III\pg_restore.exe -i -h
> localhost -p 5432 -U postgres -d a_db -a -t pictures -v
> "D:\a_db.backup"
>
> pg_restore: connecting to database for restore
>
> pg_restore: restoring data for table " pictures"
>
> pg_restore: [custom archiver] error during file seek: Invalid argument
>
> pg_restore: *** aborted because of error
>
>
>
> Process returned exit code 1.
Have you tried using psql to restore? This almost sounds like you're
hitting a file size limit somewhere, like the 2 gig file size limit
linux kernels suffered from years ago.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2005-08-30 18:11 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-08-21 21:16 DB restore fails W2k. Dan <danilos@home.se>
2005-08-30 18:11 ` Scott Marlowe <smarlowe@g2switchworks.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox