From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
---|---|
To: | Gary Stainburn <gary(dot)stainburn(at)ringways(dot)co(dot)uk> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Postgresql not accessible, recovering |
Date: | 2013-11-20 10:57:13 |
Message-ID: | CAKoxK+7hCVfUAAjdHqo_ZCNGeWXdLGAYLdj2feB77eVWcY9Vww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Nov 19, 2013 at 3:39 PM, Gary Stainburn
<gary(dot)stainburn(at)ringways(dot)co(dot)uk> wrote:
> On Tuesday 19 November 2013 14:25:44 bricklen wrote:
> LOG: received smart shutdown request
> LOG: shutting down
> LOG: database system is shut down
> LOG: database system was shut down in recovery at 2013-11-19 10:22:59 GMT
> LOG: database system was not properly shut down; automatic recovery in
> progress
Are you shutting down the database while recovery is in progress or is
there any tool that is doing that for you? I mean, the recovery could
be taking so long because something is kicking it away before it is
finished?
For what I know recovery should be kind of proprotional to the
checkpoint configurations, have you changed such settings to get very
high windows over checkpoints?
Luca
From | Date | Subject | |
---|---|---|---|
Next Message | Karl Hafner | 2013-11-20 14:20:48 | Re: MultiXactId Error in Autovacuum |
Previous Message | Albe Laurenz | 2013-11-19 14:55:00 | Re: MultiXactId Error in Autovacuum |