Re: Exit walsender before confirming remote flush in logical replication
От | Amit Kapila |
---|---|
Тема | Re: Exit walsender before confirming remote flush in logical replication |
Дата | |
Msg-id | CAA4eK1LEM+GJfgh4AjBZiqUqRozHqfgCf6CpKWR2BoiVO69KoQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Exit walsender before confirming remote flush in logical replication (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Exit walsender before confirming remote flush in logical replication
|
Список | pgsql-hackers |
On Tue, Feb 7, 2023 at 2:04 AM Andres Freund <andres@anarazel.de> wrote: > > On 2023-02-06 12:23:54 +0530, Amit Kapila wrote: > > On Mon, Feb 6, 2023 at 10:33 AM Andres Freund <andres@anarazel.de> wrote: > > > Smart shutdown is practically unusable. I don't think it makes sense to tie behavior of walsender to it in any way. > > > > > > > So, we have the following options: (a) do nothing for this; (b) > > clarify the current behavior in docs. Any suggestions? > > b) seems good. > > I also think it'd make sense to improve this on a code-level. Just not in the > wholesale way discussed so far. > > How about we make it an option in START_REPLICATION? Delayed logical rep can > toggle that on by default. > Works for me. So, when this option is set in START_REPLICATION message, walsender will set some flag and allow itself to exit at shutdown without waiting for WAL to be sent? -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: