[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] Archiver behavior at shutdown
From:       Simon Riggs <simon () 2ndquadrant ! com>
Date:       2007-12-29 12:36:50
Message-ID: 1198931810.9558.92.camel () ebony ! site
[Download RAW message or body]

On Fri, 2007-12-28 at 20:20 -0500, Greg Smith wrote:
> On Sat, 29 Dec 2007, Simon Riggs wrote:
> 
> > System Shutdown
> > System shuts down, postmaster shuts down, archiver works furiously until
> > the end trying to archive things away. Archiver gets caught half way
> > through copy, so crashes, leaving archiver.pid. Subsequent startup sees
> > archiver.pid, postmaster reads file to get pid, then sends signal to
> > archiver to see if it is still alive, it isn't so remove archiver.pid
> > and allow next archiver to start.
> 
> Isn't it possible some other process may have started with that pid if the 
> database server was down for long enough?  In that case sending a signal 
> presuming it's the archive process that used to have that pid might be bad 
> form.

I think you've emphasised my point that me rushing this in the time I
have available is not going to improve matters for the group.

My original one line change described on bug 3843 seems like the best
solution for 8.3.

-- 
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match
[prev in list] [next in list] [prev in thread] [next in thread]