Re: [HACKERS] logical replication and PANIC during shutdowncheckpoint in publisher
От | Fujii Masao |
---|---|
Тема | Re: [HACKERS] logical replication and PANIC during shutdowncheckpoint in publisher |
Дата | |
Msg-id | CAHGQGwE+-n_=aq5pepo3tAdyteraxV4R2sJ1ZNZ1iS2KDmOQBw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] logical replication and PANIC during shutdowncheckpoint in publisher (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] logical replication and PANIC during shutdowncheckpoint in publisher
|
Список | pgsql-hackers |
On Thu, Apr 13, 2017 at 5:25 AM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > On 4/12/17 09:55, Fujii Masao wrote: >> To fix this issue, we should terminate walsender for logical replication >> before shutdown checkpoint starts. Of course walsender for physical >> replication still needs to keep running until shutdown checkpoint ends, >> though. > > Can we turn it into a kind of read-only or no-new-commands mode instead, > so it can keep streaming but not accept any new actions? So we make walsenders switch to that mode and wait for all the already-ongoing their "write" commands to finish, and then we start a shutdown checkpoint? This is an idea, but seems a bit complicated. ISTM that it's simpler to terminate only walsenders for logical rep before shutdown checkpoint. Regards, -- Fujii Masao
В списке pgsql-hackers по дате отправления: