Обсуждение: Re: Logical Replication in Postgres 10.4

Hi all,

I have a doubt in Logical Replication feature in 10.4.  I have 2 servers
where in which I have configured "Logical Replication" between two databases
source and destination.

*In the Source*:
Before creating publication on publisher I have create 2 tables on both
publisher & subscriber. But only publisher contains data. 

Later, I have create publication for all tables using the below command:
CREATE PUBLICATION mypub FOR ALL TABLES;

*In the Target*:
In the subscriber server, I have created a subscription for that
publication. 

Suddenly within no time the data got replicated(happy for that).

The actual problem now aroused. I again went on creating a new table on the
primary but it was not part of my publication(surprised). So it was not
replicated.

But from the documentation "FOR ALL TABLES" option the futurely created
tables are also part of the replication which was not (3'rd table) in my
case.

What went wrong? Kindly help me out!!!

Thanks in Advance!

Regards,
Pavan



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html

Hi all,

I have a doubt in Logical Replication feature in 10.4.  I have 2 servers
where in which I have configured "Logical Replication" between two databases
source and destination.

*In the Source*:
Before creating publication on publisher I have create 2 tables on both
publisher & subscriber. But only publisher contains data. 

Later, I have create publication for all tables using the below command:
CREATE PUBLICATION mypub FOR ALL TABLES;

*In the Target*:
In the subscriber server, I have created a subscription for that
publication. 

Suddenly within no time the data got replicated(happy for that).

The actual problem now aroused. I again went on creating a new table on the
primary but it was not part of my publication(surprised). So it was not
replicated.

But from the documentation "FOR ALL TABLES" option the futurely created
tables are also part of the replication which was not (3'rd table) in my
case.

What went wrong? Kindly help me out!!!

ALTER SUBSCRIPTION name REFRESH PUBLICATION WITH ( COPY_DATA );

Thanks in Advance!

Regards,
Pavan



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html

-- 
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

Hi Achilleas,

>Did you refresh the subscription ? :
>ALTER SUBSCRIPTION name REFRESH PUBLICATION WITH ( COPY_DATA );

Yes, I have performed the above step on the subscriber. But still it is not
replicating. 

Help me out of this. This needs to be implemented in production ASAP.


Thanks in Advance.

Regards,
Pavan



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html

Hi all,

One temporary workaround I found was dropping the subscription and
recreating it again.

Then it started syncing the tables between publisher and subscriber. But
don't know whether it is apt solution to implement here!!

Thanks in Advance!


Regards,
Pavan



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html

On 13/08/2018 16:16, pavan95 wrote:
> Hi all,
>
> One temporary workaround I found was dropping the subscription and
> recreating it again.
>
> Then it started syncing the tables between publisher and subscriber. But
> don't know whether it is apt solution to implement here!!
>
> Thanks in Advance!
Did you delete the rows from all subscribed tables in the subscriber side in order to start from scratch? (avoid
duplicateERRORs, etc)?
 
>
>
> Regards,
> Pavan
>
>
>
> --
> Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
>

-- 
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt

> Hi all, 
> 
> One temporary workaround I found was dropping the subscription and 
> recreating it again. 
> 
> Then it started syncing the tables between publisher and subscriber. But 
> don't know whether it is apt solution to implement here!! 
> 
> Thanks in Advance! 
>>Did you delete the rows from all subscribed tables in the subscriber side
in order to start from scratch? (avoid duplicate ERRORs, etc)?

Yes

> 
> 
> Regards, 
> Pavan 
> 
> 



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html