Re: Help, server doesn't start
От | René Romero Benavides |
---|---|
Тема | Re: Help, server doesn't start |
Дата | |
Msg-id | 4FE7E967.4010408@gmail.com обсуждение исходный текст |
Ответ на | Help, server doesn't start ("Anibal David Acosta" <aa@devshock.com>) |
Ответы |
Re: Help, server doesn't start
|
Список | pgsql-general |
We have an old postgres installation (8.3) running on windows 2003
The server run perfect for many years but today it crash L
We have a very old backup so I’ll try desperate to repair.
If I can’t repair I want to skip the error and start server with only healthy data, no matter if I lose some table page, entire table or even entire database because the server has many databases inside.
Currently the database is not starting, when I try to start I got the in the log:
2012-06-25 02:22:33 GMT LOG: database system was interrupted while in recovery at 2012-06-25 02:22:26 GMT
2012-06-25 02:22:33 GMT HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2012-06-25 02:22:33 GMT LOG: database system was not properly shut down; automatic recovery in progress
2012-06-25 02:22:33 GMT LOG: redo starts at 17C/E1C42040
2012-06-25 02:22:33 GMT LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
2012-06-25 02:22:33 GMT FATAL: the database system is starting up
[LAST TWO LINES REPEAT MANY TIMES]
2012-06-25 02:22:36 GMT LOG: startup process (PID 1120) was terminated by exception 0xC000000D
2012-06-25 02:22:36 GMT HINT: See C include file "ntstatus.h" for a description of the hexadecimal value.
2012-06-25 02:22:36 GMT LOG: aborting startup due to startup process failure
2012-06-25 02:22:36 GMT FATAL: the database system is starting up
2012-06-25 02:22:36 GMT LOG: loaded library "$libdir/plugins/plugin_debugger.dll"
2012-06-25 02:22:36 GMT FATAL: the database system is starting up
The first advice here is:
- backup your data files before any attempt to fix the issue.
It might be a hardware failure that corrupted your data (specifically your transaction logs).
It might be a bug on that specific version, what is your minor release number?
- As a last resort you could use pg_resetlog, it's a binary that resets the information in the control file and transaction logs.
http://www.postgresql.org/docs/8.3/static/app-pgresetxlog.html
but please backup your data directory first.
After that, if the server starts up successfully, perform a pg_dump / pg_dumpall A.S.A.P and reload your data on a new data cluster.
I'm on twitter @iCodeiExist
В списке pgsql-general по дате отправления: