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

Re: Archiver behavior at shutdown

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Archiver behavior at shutdown
Date: 2007-12-29 12:36:50
Message-ID: (view raw or whole thread)
Lists: pgsql-hackerspgsql-patches
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 Subsequent startup sees
> >, postmaster reads file to get pid, then sends signal to
> > archiver to see if it is still alive, it isn't so remove
> > 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

In response to


pgsql-hackers by date

Next:From: D'Arcy J.M. CainDate: 2007-12-29 14:34:42
Subject: Re: Spoofing as the postmaster
Previous:From: Magnus HaganderDate: 2007-12-29 11:57:26
Subject: Re: Spoofing as the postmaster

pgsql-patches by date

Next:From: Bruce MomjianDate: 2007-12-29 17:57:56
Subject: Re: DOC: Wal update
Previous:From: Bruce MomjianDate: 2007-12-29 04:15:57
Subject: Re: Doc-patch: PAM authentication fails for local UNIX users

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