Thread: pg_restore problem "Found unexpected Block id"
Hi , I am getting an error while restoring the Database Backup. I am postgre sql 8.0 with Windows XP O.S. while restoring the data i am getting pg_restore: [custom archiver] found unexpected block ID (0) when reading data -- expected 4034 Plz provide any solution. Thanks in advance -- View this message in context: http://postgresql.1045698.n5.nabble.com/pg-restore-problem-Found-unexpected-Block-id-tp5723501.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
"ramana.pls" <ramana.pls@gmail.com> writes:
> I am getting an error while restoring the Database Backup. I am postgre sql
> 8.0 with Windows XP O.S.
8.0? You do know that's been out of support for several years now,
right?
> while restoring the data i am getting
> pg_restore: [custom archiver] found unexpected block ID (0) when reading
> data --
> expected 4034
This looks somewhat like a pg_restore bug we fixed awhile back. I'd
suggest updating to a more modern Postgres version and seeing if it
works any better.
regards, tom lane
"ramana.pls" <ramana.pls@gmail.com> wrote: > I am getting an error while restoring the Database Backup. I am > postgre sql 8.0 with Windows XP O.S. PostgreSQL version 8.0 has been out of support overall for years, and out of support for Windows for years before that. http://archives.postgresql.org/pgsql-announce/2008-01/msg00005.php http://www.postgresql.org/support/versioning/ Once you get past the immediate problems, it is extremely important that you update to a supported version and stay up-to-date with minor (bug-fix) releases. Regarding the immediate problem, your report could use a lot more detail. What steps have you taken to get to where you are now? Exactly what version of PostgreSQL is this (8.0.what?)? http://wiki.postgresql.org/wiki/Guide_to_reporting_problems Without knowing more, it's hard to give much advice. -Kevin
[copying the list; please keep the list copied on all replies] Ramana Panda <ramana.pls@gmail.com> wrote: > I am using the Version : *"PostgreSQL 8.0.0 on i686-pc-mingw32, > compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)"* You didn't even keep up on bug fix releases? It's amazing that your database is still running. > It is a running application. It is very difficult to update all at > once. I need to change the front end also. You are in danger of losing all your data without having a usable backup. Consider how difficult that position will be by comparison. > Sorry for inconvinience. No need to apologize; it won't have much impact on me when your data is lost. > I have taken backup on 09-09-2012. it is working fine. Whatever you do, don't overwrite or delete that backup! That may be something you will need to use for recovery. > with 10th Sep Backup, while restoring it is giving error message > after some tables restored: > > *pg_restore: [custom archiver] found unexpected block ID (0) when > reading data -- expected 4034 > * > O.S. Version : Windows XP with Service Pack 3 If the data in this database has any value to you, you should upgrade to *at least* the last version of 8.2 *IMMEDIATELY*, since that's the release where some very serious bugs related to Windows were fixed. Try running the pg_dump version from the newer version, and you might still be able to back up recent work; otherwise you will need to restore from your last usable backup and redo all work from that point on. 8.2 went out of support last year, but it would be a huge step forward in stability on Windows without any major incompatibilities for application code, and should buy you a little time to deal with working through some of the bumps in converting to later versions. You should really be targeting the 9.1 release at this point. -Kevin