On 05/25/2017 03:38 PM, tushar wrote:
While performing - Alter subscription..SET , I found that NOTICE message is coming duplicate next time , which is not needed anymore.
There is an another example - where i am getting "ERROR: subscription table 16435 in subscription 16684 does not exist" in standby log file


2017-05-25 13:51:48.825 BST [32138] NOTICE: removed subscription for table public.t96 2017-05-25 13:51:48.825 BST [32138] NOTICE: removed subscription for table public.t97 2017-05-25 13:51:48.826 BST [32138] NOTICE: removed subscription for table public.t98 2017-05-25 13:51:48.826 BST [32138] NOTICE: removed subscription for table public.t99 2017-05-25 13:51:48.826 BST [32138] NOTICE: removed subscription for table public.t100 2017-05-25 13:51:48.827 BST [32138] LOG: duration: 35.404 ms statement: alter subscription c1 set publication p1 refresh; 2017-05-25 13:51:49.192 BST [32347] LOG: starting logical replication worker for subscription "c1" 2017-05-25 13:51:49.198 BST [32368] LOG: logical replication sync for subscription c1, table t16 started 2017-05-25 13:51:49.198 BST [32368] ERROR: subscription table 16429 in subscription 16684 does not exist 2017-05-25 13:51:49.199 BST [32347] LOG: starting logical replication worker for subscription "c1" 2017-05-25 13:51:49.200 BST [32065] LOG: worker process: logical replication worker for subscription 16684 sync 16429 (PID 32368) exited with exit code 1 2017-05-25 13:51:49.204 BST [32369] LOG: logical replication sync for subscription c1, table t17 started 2017-05-25 13:51:49.204 BST [32369] ERROR: subscription table 16432 in subscription 16684 does not exist 2017-05-25 13:51:49.205 BST [32347] LOG: starting logical replication worker for subscription "c1" 2017-05-25 13:51:49.205 BST [32065] LOG: worker process: logical replication worker for subscription 16684 sync 16432 (PID 32369) exited with exit code 1 2017-05-25 13:51:49.209 BST [32370] LOG: logical replication sync for subscription c1, table t18 started 2017-05-25 13:51:49.209 BST [32370] ERROR: subscription table 16435 in subscription 16684 does not exist 2017-05-25 13:51:49.210 BST [32347] LOG: starting logical replication worker for subscription "c1" 2017-05-25 13:51:49.210 BST [32065] LOG: worker process: logical replication worker for subscription 16684 sync 16435 (PID 32370) exited with exit code 1 2017-05-25 13:51:49.213 BST [32371] LOG: logical replication sync for subscription c1, table t19 started 2017-05-25 13:51:49.213 BST [32371] ERROR: subscription table 16438 in subscription 16684 does not exist 2017-05-25 13:51:49.214 BST [32347] LOG: starting logical replication worker for subscription "c1"


Steps to reproduce -
X cluster ->
create 100 tables , publish all tables (create publication pub for table t1,t2,t2..........t100;) create one more table (create table t101(n int), create publication , publish only that table (create publication p1 for table t101;)

Y Cluster ->
create subscription (create subscription c1 connection 'host=localhost port=5432 user=centos ' publication pub;
alter subscription c1 set publication p1 refresh;
alter subscription c1 set publication pub refresh;
alter subscription c1 set publication p1 refresh;

check the log file.

--
regards,tushar
EnterpriseDB  https://www.enterprisedb.com/
The Enterprise PostgreSQL Company



--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to