RE: Handle infinite recursion in logical replication setup

Поиск
Список
Период
Сортировка
От shiy.fnst@fujitsu.com
Тема RE: Handle infinite recursion in logical replication setup
Дата
Msg-id TYAPR01MB6315ABAE19C44C50E1D30327FDBA9@TYAPR01MB6315.jpnprd01.prod.outlook.com
обсуждение исходный текст
Ответ на Re: Handle infinite recursion in logical replication setup  (vignesh C <vignesh21@gmail.com>)
Ответы Re: Handle infinite recursion in logical replication setup  (vignesh C <vignesh21@gmail.com>)
Список pgsql-hackers
On Tue, Jun 28, 2022 2:18 PM vignesh C <vignesh21@gmail.com> wrote:
> 
> Thanks for the comments, the attached  v25 patch has the changes for the
> same.
> 

Thanks for updating the patch. Here are some comments.

0002 patch:
==============
1.
+# Test the CREATE SUBSCRIPTION 'origin' parameter and its interaction with
+# 'copy_data' parameter.

It seems we should move "and its interaction with 'copy_data' parameter" to
0003 patch.

0003 patch
==============
1.
When using ALTER SUBSCRIPTION ... REFRESH, subscription will throw an error if
any table is subscribed in publisher, even if the table has been subscribed
before refresh (which won't do the initial copy when refreshing). It looks the
previously subscribed tables don't need this check. Would it be better that we
only check the tables which need to do the initial copy?

2.
+                errmsg("table:%s.%s might have replicated data in the publisher",
+                       nspname, relname),

I think the table name needs to be enclosed in double quotes, which is
consistent with other messages.

Regards,
Shi yu

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Backup command and functions can cause assertion failure and segmentation fault
Следующее
От: Nikolay Shaplov
Дата:
Сообщение: Re: [PATCH] minor reloption regression tests improvement