Re: Changing PK on replicated database

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: PegoraroF10 <marcos(at)f10(dot)com(dot)br>, pgsql-general(at)postgresql(dot)org
Subject: Re: Changing PK on replicated database
Date: 2019-10-16 22:14:29
Message-ID: 6336a5c2-5289-43a7-d434-15e312ed271d@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-10-16 22:31:38 Re: CVE-2018-1058
Previous Message Adrian Klaver 2019-10-16 22:09:48 Re: CVE-2018-1058