Re: Changing PK on replicated database - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Changing PK on replicated database
Date
Msg-id 6336a5c2-5289-43a7-d434-15e312ed271d@aklaver.com
Whole thread Raw
In response to Changing PK on replicated database  (PegoraroF10 <marcos@f10.com.br>)
Responses Re: Changing PK on replicated database
List pgsql-general
On 10/16/19 1:47 PM, PegoraroF10 wrote:
> I have replication using Publication/Subscription and configured with REPLICA
> IDENTITY DEFAULT, so it uses PK values to do the replication. Then, I´ve
> imported data in a new schema and that has several tables with a record with
> its PK = 0. Replication works but my application doesn´t because it needs to
> see pk values > 0.
> 
> So, I have to change those records with 0 on their pk to any value, what is
> the best way to do that ?
> If i just change pk valued on master how will the data of that record be
> replicated ?
> That record will be sent to replica as update but that PK doesn´t exist on
> replica server, so ...

I'm not following. You said above the replication worked with the 
records where PK = 0, it was your application that could not find them. 
If that is true then the records should be on the replica server, 
correct? In that case it would just be an update.
> 
> Or do I need to update them manually on Master and Replicated servers ?
> 
> I didn´t find any info about this on Docs and because that I´m posting about
> this.
> 
> 
> 
> --
> Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
> 
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: CVE-2018-1058
Next
From: Adrian Klaver
Date:
Subject: Re: CVE-2018-1058