| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | antonio(dot)v(dot)botelho(at)gmail(dot)com |
| Subject: | logial replication - drop subscription. |
| Date: | 2025-05-28 20:20:51 |
| Message-ID: | 174846365177.780.12843663746002009140@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/sql-droppublication.html
Description:
Hi,
I'm using a lot the logical replication.
I have to do some DDL changes, via an automatic process, on the primary.
That process drop the existing publication, which will stop the
subscription.
I kept the LSN information on the primary, perform the DDL changes on the
replica.
Than I recreate the publication, use the pg_replication_slot_advance using
the savec LSN.
When I re-enable the subscription, I have an error message in the postgres
log saying that the publication doesn't exist. However, it does have the
same name.
Can a note be added on the "DROP PUBLICATION" page to mention that dropping
a publication will compromise the logical replication process event if the
publication is recreated with the same name.
Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | LUC PHEMBA | 2025-05-31 19:58:33 | PostgreSQL 17 default value assignment doesn't work in pgAdmin4 v9.4 |
| Previous Message | Laurenz Albe | 2025-05-28 18:49:52 | Re: Documentation should state what happens, when a commit fails |