| From: | Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
|---|---|
| To: | Cory Nemelka <cnemelka(at)gmail(dot)com> |
| Cc: | Avi Weinberg <AviW(at)gilat(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Implicit table removal from logical replication publication |
| Date: | 2021-06-10 18:58:12 |
| Message-ID: | CAM+6J97LmjZ2c2uOmR_31zweFn-FgBkQsDufUBm991vr-SYO7g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
pg_subscription_rel
pg_publication_rel
have the relation part of the publication concerned.
OP has an issue to figure out if publication has a list of tables not in
sync in subscription and has subscription broken.
there may be ways to query tables on subscriber dbs via dblink or fdw,
but there is no view of metric for individual relation level subscription
to help figure out if it is broken.
I mean like for replication slots, we have an active flag to easily figure
out issues with replication, but not with pub/sub.
I only used logical replication for upgrades, so not have little idea wrt
ddl changes issues.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2021-06-10 20:21:00 | Re: bottom / top posting |
| Previous Message | Cory Nemelka | 2021-06-10 18:43:04 | Re: Implicit table removal from logical replication publication |