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

Re: HS/SR and smart shutdown

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: HS/SR and smart shutdown
Date: 2010-01-21 01:59:00
Message-ID: 4B57B4E4.2090009@catalyst.net.nz (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>   
>> On Wed, Jan 20, 2010 at 8:44 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>>     
>>> Well, as long as streaming rep is running, you can't do a smart shutdown
>>> ... smart shutdown seems to treat the walreciever as a client
>>> connection.  At the very least, this should be in the documentation.
>>>       
>
>   
>> How hard is it to fix?
>>     
>
> I think the first question is do we *want* to fix it, or is it
> appropriate behavior?
>
> If the master shuts down, will the slaves try to fail over to become
> masters?  When the master restarts, will the slaves automatically
> reconnect?  If these questions have the wrong answers, shutting down the
> master isn't something to be done lightly, and automatically
> disconnecting slaves would be a real bad idea.
>
> 	
Right - surely people who have been using pg_standby etc have discovered 
this behaviour, so documenting it is fine I would think.

regards

Mark

In response to

pgsql-hackers by date

Next:From: Takahiro ItagakiDate: 2010-01-21 02:02:16
Subject: Re: Fix auto-prepare #2
Previous:From: Robert HaasDate: 2010-01-21 01:58:19
Subject: Re: HS/SR and smart shutdown

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