Search Postgresql Archives

Re: pg_restore: [archiver] entry ID -825110830 out of range -- perhaps a corrupt TOC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Greetings;

And thanks for your reply!  I tried the following:

less xaa | grep "^;"
"xaa" may be a binary file.  See it anyway? y

Binary file (standard input) matches


And so am not sure which version I did the following from:

pg_dump -c -F c -Z 9 [databasename]


But I installed it about a year ago, so whichever was the release then.
Am trying to restore to the following:

postgresql-client-7.4.21 PostgreSQL database (client)
postgresql-plpython-7.4.21_1 A module for using Python to write SQL functions
postgresql-server-7.4.21 The most advanced open-source database available anywhere

As follows:

cat * | pg_restore -d [databasename]


And the following error's exactly what happens:

"pg_restore: [archiver] entry ID -825110830 out of range -- perhaps a corrupt TOC"


It's worked for me many years before, but am now concerned that I've maybe just lost this database, so any help would be so greatly appreciated and thank you again so much!



On Tue, Jan 20, 2009 at 12:30 AM, Andreas Wenk <a.wenk@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

maybe I did not understand - but what exactly happens when you do something like

pg_restore -d databasename -L backup.toc backup.bak (bak -> or what ever custom format you
use)

Is the version you did the backup with the same like the postgres version you want to
restore to? I am not sure, but maybe there are occuring some problems ...

$ less test.toc | grep "^;"
[...]
;     Dumped from database version: 8.3.5
;     Dumped by pg_dump version: 8.3.5
[...]

Cheers

Andy
- --
St.Pauli - Hamburg - Germany

Andreas Wenk

Dennis C schrieb:
> Greetings:
>
> I already did some searches on the "pg_restore: [archiver] entry ID
> -825110830 out of range -- perhaps a corrupt TOC" error and am still not
> sure why my database's not restoring after upgrading the FreeBSD and
> select ports such as PostGreSQL.  I did see something from a long time
> ago about altering the table, especially column names, quite possibly
> being a problem and I have done a lot of that, but as many backups as
> I've also done this past year, this' the first time I've had to use the
> restore again and am now not even sure how to get my database back.  If
> this seems familiar and simple enough for anyone, please advise
> including which details may be useful here.
>
> Thanks,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJdYu7Va7znmSP9AwRAunPAKCliM90HkrNzQ51ectMmziqc7gTGwCeNrco
VvYrDL/hbinlF9gaPUMau1o=
=M8mK
-----END PGP SIGNATURE-----

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux