Re: wait event and archive_command
От | Bharath Rupireddy |
---|---|
Тема | Re: wait event and archive_command |
Дата | |
Msg-id | CALj2ACVbPU2sUKS_-ocpSO1=0bvZzpK2oppR5p+bz9xeoQtpJw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: wait event and archive_command (Fujii Masao <masao.fujii@oss.nttdata.com>) |
Ответы |
Re: wait event and archive_command
|
Список | pgsql-hackers |
On Thu, Nov 18, 2021 at 7:53 AM Fujii Masao <masao.fujii@oss.nttdata.com> wrote: > > 1) Can't we determine the wait event type based on commandName in > > ExecuteRecoveryCommand instead of passing it as an extra param? > > Yes, that's possible. But isn't it uglier to make ExecuteRecoveryCommand() have > the map of command name and wait event? So I feel inclined to avoid adding > something like the following code into the function... Thought? > > if (strcmp(commandName, "recovery_end_command") == 0) > wait_event_info = WAIT_EVENT_RECOVERY_END_COMMAND; > else if (strcmp(commandName, "archive_command_command") == 0) Yeah let's not do that. I'm fine with the wait_event_for_archive_command_v2.patch as is. Regards, Bharath Rupireddy.
В списке pgsql-hackers по дате отправления: