Skip site navigation (1) Skip section navigation (2)

Re: Hung postmaster (8.3.9)

From: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Hung postmaster (8.3.9)
Date: 2010-02-28 06:15:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
On Saturday 27 February 2010 @ 22:18, Greg Smith wrote:
> Ed L. wrote:
> > 2010-02-27 20:11:10.426 CST [23134]    LOG:  database system
> > was not properly shut down; automatic recovery in progress
> > 2010-02-27 20:11:10.497 CST [23134]    LOG:  record with
> > zero length at 8BC/63F6020 2010-02-27 20:11:10.497 CST
> > [23134]    LOG:  redo is not required
> If the server is hung at this point, it was doing something: 
>  recovery from a crash, and during that period it will not
>  respond to statements until it's finished as you noted.  That
>  can take some time, could run into the minutes.  And if you
>  kill it, next time the process starts all over again having
>  made no progress.
> I'd try starting the server again, confirm it's only after
>  this point it pauses at, watching if it's doing something
>  with "top -c", and grab some backtraces of what it's doing
>  then.  In this sample you gave, the shutdown was too fast for
>  the server have done very recovery before it was killed off. 
>  It may just be you need to let it sit there for a while to
>  finish recovery and then it will be fine again, can't tell
>  from the data you've provided so far.

Good point from my example, but it hung like that for 8 hours, 
and seems to be ready to do so again.

In response to

pgsql-general by date

Next:From: ThomasDate: 2010-02-28 10:26:02
Subject: does writer process also write data to WAL log files ?
Previous:From: Greg SmithDate: 2010-02-28 05:18:41
Subject: Re: Hung postmaster (8.3.9)

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group