Re: BUG #9756: Inconsistent database after OS restart

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: sdl(at)mnppsaturn(dot)ru
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #9756: Inconsistent database after OS restart
Date: 2014-03-28 17:39:52
Message-ID: CAMkU=1zud6zCnAch1iggy8Lfx9KJNLe6iN5qusv1vJp5WNJtXw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Mar 28, 2014 at 12:58 AM, <sdl(at)mnppsaturn(dot)ru> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 9756
> Logged by: Dmitry Samokhin
> Email address: sdl(at)mnppsaturn(dot)ru
> PostgreSQL version: 9.2.8
> Operating system: Windows XP, 7
> Description:
>
> After every Windows restart, database couldn't be shut down properly and
> recovering actions are performed on the next startup. But if we control the
> service manually by the Windows Services snap-in, no problem with the
> correct DB cluster shutdown. Looks like there's something wrong with the
> correct autovacuum process shutdown which leads to the DB inconsistency.
>
>
> *** Windows restart: ***
>
> -- Stopping:
> 2014-03-28 11:37:34 MSK LOG: received fast shutdown request
> 2014-03-28 11:37:34 MSK LOG: aborting any active transactions
> 2014-03-28 11:37:34 MSK LOG: autovacuum launcher shutting down
> 2014-03-28 11:37:34 MSK ERROR: canceling statement due to user request
>

It looks like Windows told the server to shutdown, but did not give it
enough time to complete the process before killing it uncleanly.

Can you make Windows shutdown more patient?

Cheers,

Jeff

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mike Blackwell 2014-03-28 21:36:49 Re: BUG #9518: temporary login failure - "missing pg_hba entry"
Previous Message Bruce Momjian 2014-03-28 16:55:12 Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd