RE: Skipping logical replication transactions on subscriber side
От | houzj.fnst@fujitsu.com |
---|---|
Тема | RE: Skipping logical replication transactions on subscriber side |
Дата | |
Msg-id | OS0PR01MB57164AD9495E723AC6E1407994FD9@OS0PR01MB5716.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | RE: Skipping logical replication transactions on subscriber side ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>) |
Ответы |
Re: Skipping logical replication transactions on subscriber side
|
Список | pgsql-hackers |
Monday, August 16, 2021 3:00 PM Hou, Zhijie wrote: > On Thu, Aug 12, 2021 1:53 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > I've attached the updated patches. FYI I've included the patch > > (v8-0005) that fixes the assertion failure during shared fileset > > cleanup to make cfbot tests happy. > > Hi, > > Thanks for the new patches. > I have a few comments on the v8-0001 patch. > 3) > Do we need to invoke set_apply_error_context_xact() in the function > apply_handle_stream_prepare() to save the xid and timestamp ? Sorry, this comment wasn't correct, please ignore it. Here is another comment: +char * +logicalrep_message_type(LogicalRepMsgType action) +{ ... + case LOGICAL_REP_MSG_STREAM_END: + return "STREAM END"; ... I think most the existing code use "STREAM STOP" to describe the LOGICAL_REP_MSG_STREAM_END message, is it better to return "STREAM STOP" in function logicalrep_message_type() too ? Best regards, Hou zj
В списке pgsql-hackers по дате отправления: