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

Re: Revised patch for fixing archiver shutdown behavior

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-patches(at)postgreSQL(dot)org
Subject: Re: Revised patch for fixing archiver shutdown behavior
Date: 2008-01-11 14:54:38
Message-ID: 12873.1200063278@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> If we do a shutdown immediate on the postmaster *after* the bgwriter has
> written a shutdown checkpoint, do we have any record that there was a
> panic stop? Do we enter recovery in that case? I think the answers are
> yes and no, but just checking.

Yeah, the postmaster would complain at exit, but the pg_control state
is already SHUTDOWN at that point.  There'd be a log entry showing
abnormal archiver exit if the panic had had any actual effect on it.

			regards, tom lane

In response to

pgsql-patches by date

Next:From: Tom LaneDate: 2008-01-12 23:35:16
Subject: Re: BUG #3860: xpath crashes backend when is querying xmlagg result
Previous:From: Simon RiggsDate: 2008-01-11 08:26:31
Subject: Re: Revised patch for fixing archiver shutdown behavior

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