| From: | Kashif Zeeshan <kashi(dot)zeeshan(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:01:25 |
| Message-ID: | CAAPsdhcMe40ME2Fp1jzy6AmfaRkhRMSqpx7j9AEgNcpbHwmfFg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi Siraj
It all depends on your requirements, you can use as many publication as
you want as per your requirements.
Regards
Kashif Zeeshan
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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Muhammad Ikram | 2024-06-24 04:02:04 | Re: Logical replication troubleshooting |
| Previous Message | Siraj G | 2024-06-24 02:50:08 | Logical replication troubleshooting |