Re: Online base backup from the hot-standby - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Online base backup from the hot-standby
Date
Msg-id CA+U5nM+h-Kty2HDOntn5Om+XU_0N5ZN5uvXzSR0YXnzrEUBwQw@mail.gmail.com
Whole thread Raw
In response to Re: Online base backup from the hot-standby  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Online base backup from the hot-standby  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Wed, Jan 25, 2012 at 8:49 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Wed, Jan 25, 2012 at 8:16 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
>
>>> What happens if we shutdown the WALwriter and then issue SIGHUP?
>>
>> SIGHUP doesn't affect full_page_writes in that case. Oh, you are concerned about
>> the case where smart shutdown kills walwriter but some backends are
>> still running?
>> Currently SIGHUP affects full_page_writes and running backends use the changed
>> new value of full_page_writes. But in the patch, SIGHUP doesn't affect...
>>
>> To address the problem, we should either postpone the shutdown of walwriter
>> until all backends have gone away, or leave the update of full_page_writes to
>> checkpointer process instead of walwriter. Thought?
>
> checkpointer seems the correct place to me


Done.


--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: GUC_REPORT for protocol tunables was: Re: Optimize binary serialization format of arrays with fixed size elements
Next
From: Robert Haas
Date:
Subject: Re: [v9.2] LEAKPROOF attribute of FUNCTION (Re: [v9.2] Fix Leaky View Problem)