From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: sync rep and smart shutdown |
Date: | 2011-04-11 02:56:03 |
Message-ID: | BANLkTimCqyEH3YQtVgFFEbQbA5UTzKEUow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Apr 9, 2011 at 3:53 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> There are a couple of plausible ways to proceed here:
>>
>>> 1. Do nothing.
>>
>>> 2. When a smart shutdown is initiated, shut off synchronous
>>> replication.
>>
>>> 3. Accept new replication connections even when the system is
>>> undergoing a smart shutdown.
>>
>> I agree that #3 is impractical and #2 is a bad idea, which seems to
>> leave us with #1 (unless anyone has a #4)? This is probably just
>> something we should figure is going to be one of the rough edges
>> in the first release of sync rep.
>
> That's kind of where my mind was headed too, although I was (probably
> vainly) hoping for a better option.
Though I proposed #3, I can live with #1 for now. Even if smart shutdown
gets stuck, we can resolve that by requesting fast shutdown or emptying
synchronous_standby_names.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | YAMAMOTO Takashi | 2011-04-11 03:57:19 | Re: SSI bug? |
Previous Message | Andrew Dunstan | 2011-04-11 02:17:29 | Re: [COMMITTERS] pgsql: Don't make "replication" magical as a user name, only as a datab |