Sounds like you have a corrupt wal files that you will have to reset the
wal logs with pgresetxlog.
This will result in missing transactions so before you do this shutdown
postgres and make a copy of the database files first. That way if you
don't like what happens you can always go back to the way things were.
Also right now would be a good time to evaluate your backup strategy,
which is a different topic for a different thread, but I can certainly
help with that as well.
> version Postgresql 9.1.1 on centos5 x64
> We experience slow performance and found the server is running 3 vacuum
> process on the same db which use up 99% of CPU.
> Then we kill -9 one of those process which cause postgresql to crash and
> tried to restart after the crash
> However when the starting process reach the last WAL files, it just stuck
> pg_controldata shows the db is in Archive Recovery mode and when using
> to connect the db, it says FATAL: the database system starting up.
> I took a chance and upgrade to PostgreSql 9.1.2 and see if anything
> it still stuck at the end of recovery.
> pg_controldata shows db is in Crash recovery, but that probably different
> wording I think
> using psql to connect the db, it says FATAL: the database system is
> starting up.
> I pretty much run out of idea here.
> Can anyone help what to go from here?
In response to
pgsql-admin by date
|Next:||From: Alexander Fortin||Date: 2012-01-19 15:04:30|
|Subject: Re: Interpreting pg_stat_replication values|
|Previous:||From: Samuel Hwang||Date: 2012-01-19 00:33:37|
|Subject: Help! PostgreSQL stuck at starting up after crash|