From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Archiver behavior at shutdown |
Date: | 2007-12-27 22:52:02 |
Message-ID: | 1198795922.4221.429.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Thu, 2007-12-27 at 17:29 -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > What does postmaster do then? Sleep until archiver is done, or exit
> > immediately and hope that the archiver goes away as soon as it finishes?
>
> I think it can just exit immediately, particularly if we invent the
> variant signal for "archive what you can and then quit".
>
> > If the former, then we open the possibility that postmaster lives far
> > too long before system shutdown decides to SIGKILL it. If the latter,
> > then a subsequent postmaster start could initiate a second archiver
> > process which would cause issues with whatever the first archiver is
> > doing.
>
> That's a problem that the archiver itself should fix (perhaps it needs
> its own lockfile).
http://archives.postgresql.org/pgsql-hackers/2006-05/msg00920.php
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas 'ads' Scherbaum | 2007-12-27 23:20:38 | Re: Binary data type with other output method |
Previous Message | James Mansion | 2007-12-27 22:41:37 | Re: Sorting Improvements for 8.4 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-12-27 23:54:15 | Re: Archiver behavior at shutdown |
Previous Message | Tom Lane | 2007-12-27 22:29:29 | Re: Archiver behavior at shutdown |