| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Infinite loop on master shutdown |
| Date: | 2018-05-17 16:20:01 |
| Message-ID: | 20180517162001.rzd7l6g2h66hvzvd@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-05-17 17:19:00 +0900, Kyotaro HORIGUCHI wrote:
> Hello, as in pgsql-bug ML.
>
> https://www.postgresql.org/message-id/20180517.170021.24356216.horiguchi.kyotaro@lab.ntt.co.jp
>
> Master can go into infinite loop on shutdown. But it is caused by
> a broken database like storage rolled-back one. (The steps to
> replay this is shown in the above mail.)
>
> I think this can be avoided by rejecting a standby if it reports
> that write LSN is smaller than flush LSN after catching up.
>
> Is it worth fixing?
I'm very doubtful. If you do bad stuff to a standby, bad things can
happen...
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arthur Zakirov | 2018-05-17 16:27:18 | Re: [PROPOSAL] Shared Ispell dictionaries |
| Previous Message | Tom Lane | 2018-05-17 16:17:43 | Re: [BUGFIX] amcanbackward is not checked before building backward index paths |