From: Gary Stainburn <gary.stainburn@ringways.co.uk>
Organization: Ringways Garages Ltd
To: pgsql-admin@postgresql.org
Subject: Re: Postgresql not accessible, recovering
Date: Tue, 19 Nov 2013 14:45:23 +0000
User-Agent: KMail/1.9.10
References: <201311191108.18620.gary.stainburn@ringways.co.uk>
 <CAGrpgQ8dhjfStK_rFj3sJJsii7UUAnE4nW8KtqehVMn3BP3_4w@mail.gmail.com>
 <201311191439.59390.gary.stainburn@ringways.co.uk>
In-Reply-To: <201311191439.59390.gary.stainburn@ringways.co.uk>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201311191445.23399.gary.stainburn@ringways.co.uk>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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 


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin