| From: | Gary Stainburn <gary(dot)stainburn(at)ringways(dot)co(dot)uk> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Postgresql not accessible, recovering |
| Date: | 2013-11-19 14:45:23 |
| Message-ID: | 201311191445.23399.gary.stainburn@ringways.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2013-11-19 14:55:00 | Re: MultiXactId Error in Autovacuum |
| Previous Message | Gary Stainburn | 2013-11-19 14:39:59 | Re: Postgresql not accessible, recovering |