On 2019-04-03 13:44, Lou Tseng wrote:
> However, our database is about 200G and it will take a long time to
> complete the initial data copy. We would like to manually seed the
> subscriber database with data dump and then turn on the subscription
> like depesz showed in this
> post
> https://www
ricing.com/>
35 Technology Parkway South, Suite. 100
Peachtree Corners, GA 30092
From: Adrian Klaver
Sent: Wednesday, April 3, 2019 7:10 PM
To: Lou Tseng; pgsql-gene...@postgresql.org
Subject: Re: Seeded Replication
On 4/3/19 4:44 AM, Lou Tseng wrote:
> Hi,
&g
On 4/3/19 4:44 AM, Lou Tseng wrote:
Hi,
We are working on a project to set up replication from on premises
Postgresql 10.4 to Azure Postgresql services. However, our database is
about 200G and it will take a long time to complete the initial data
copy. We would like to manually seed the subs
Solutions<http://advancedpricing.com/>
35 Technology Parkway South, Suite. 100
Peachtree Corners, GA 30092
From: Pavan Teja
Sent: Wednesday, April 3, 2019 6:48 AM
To: Lou Tseng
Cc: pgsql-gene...@postgresql.org >> PG-General Mailing List
Subject: Re: Seeded Replicatio
Hi Lou,
Did you restore data on the subscriber during the first time. If yes this
error is likely to occur.
As a remedy, you need to restore only structural dump during initial
building of subscription.
Earlier the same issue was faced by me later it got resolved following the
above said approac
Hi,
We are working on a project to set up replication from on premises Postgresql
10.4 to Azure Postgresql services. However, our database is about 200G and it
will take a long time to complete the initial data copy. We would like to
manually seed the subscriber database with data dump and the
