| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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:56:12 |
| Message-ID: | 25317.1264038972@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-21 01:58:19 | Re: HS/SR and smart shutdown |
| Previous Message | Robert Haas | 2010-01-21 01:52:44 | Re: HS/SR and smart shutdown |