On Thu, Jan 26, 2012 at 3:07 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Wed, Jan 25, 2012 at 8:49 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> On Wed, Jan 25, 2012 at 8:16 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)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
Thanks a lot!!
I proposed another small patch which fixes the issue about an error message of
pg_basebackup, in this upthread. If it's reasonable, could you commit it?
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Fujii Masao||Date: 2012-01-26 06:21:47|
|Subject: Re: [COMMITTERS] pgsql: Add new replication mode
synchronous_commit = 'write'.|
|Previous:||From: Fujii Masao||Date: 2012-01-26 05:27:48|
|Subject: Re: Avoiding shutdown checkpoint at failover|