From: | Muhammad Ikram <mmikram(at)gmail(dot)com> |
---|---|
To: | Siraj G <tosiraj(dot)g(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Logical replication troubleshooting |
Date: | 2024-06-24 04:02:04 |
Message-ID: | CAGeimVqdkZzkvb0dVxkL2sJR+frp_mE1g43AS8n7YgQHOP9c-w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Siraj,
Please go through PostgreSQL documentation first to develop better
understanding.
https://www.postgresql.org/docs/current/logical-replication.html
Later you may go through some videos on Youtube or google. There are tons
of step by step examples available.
Regards,
Muhammad Ikram
Bitnine Global
On Mon, Jun 24, 2024 at 7:50 AM Siraj G <tosiraj(dot)g(at)gmail(dot)com> wrote:
> Hello Team!
>
> We are trying to migrate a on-premise PgSQL (v10) to GCP Cloud SQL's PgSQL
> (v10) via PubSub replication. I am trying to get familiar with best
> practices in this context. We built 2 publications - one for all tables
> with Primary Keys and other for non-Primary Keys. There are few archive
> tables with non-primary key are having issues in the replication. How do we
> troubleshoot this? Is it a best practice to bifurcate publications this way?
>
> Regards
> Siraj
>
--
Muhammad Ikram
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2024-06-24 08:10:53 | Re: Logical replication troubleshooting |
Previous Message | Kashif Zeeshan | 2024-06-24 04:01:25 | Re: Logical replication troubleshooting |