Re: Postgresql not accessible, recovering - Mailing list pgsql-admin

From Gary Stainburn
Subject Re: Postgresql not accessible, recovering
Date
Msg-id 201311191445.23399.gary.stainburn@ringways.co.uk
Whole thread Raw
In response to Re: Postgresql not accessible, recovering  (Gary Stainburn <gary.stainburn@ringways.co.uk>)
List pgsql-admin
Yesterday's log file contains:

FATAL:  the database system is starting up
LOG:  database system shutdown was interrupted; last known up at 2013-11-11
05:48:07 GMT
LOG:  database system was not properly shut down; automatic recovery in
progress
LOG:  redo starts at C/FD360978
FATAL:  the database system is starting up
FATAL:  the database system is starting up
FATAL:  the database system is starting up

[snip]


FATAL:  the database system is starting up
FATAL:  the database system is starting up
FATAL:  the database system is starting up
LOG:  received smart shutdown request
LOG:  shutting down
LOG:  database system is shut down


So it looks like it's been going for some time.

Sunday's log file is full of

LOG:  could not write temporary statistics file "pg_stat_tmp/pgstat.tmp": No
space left on device

So I'm guessing that was the original cause.

Presumably, it'll just take as long as it takes :-(

--
Gary Stainburn
Group I.T. Manager
Ringways Garages
http://www.ringways.co.uk


pgsql-admin by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: Postgresql not accessible, recovering
Next
From: Albe Laurenz
Date:
Subject: Re: MultiXactId Error in Autovacuum