From d1d83827ba4d8c5c87cd59a164a2c7a99f897512 Mon Sep 17 00:00:00 2001 From: Amit Kapila Date: Thu, 3 Apr 2025 14:27:13 +0530 Subject: [PATCH] Doc: Improve -R option added in e5aeed4b80. Author: Reviewed-by: Peter Smith Reviewed-by: vignesh C Discussion: https://postgr.es/m/CAHut+PvJPnaL=70SbBe3fYg2nq74Z=Yv4X=zRpUWYfOi-q6=2w@mail.gmail.com --- doc/src/sgml/ref/pg_createsubscriber.sgml | 27 ++++++++++++++--------- 1 file changed, 17 insertions(+), 10 deletions(-) diff --git a/doc/src/sgml/ref/pg_createsubscriber.sgml b/doc/src/sgml/ref/pg_createsubscriber.sgml index 1f0ddd7f9f2..73377aa6a6e 100644 --- a/doc/src/sgml/ref/pg_createsubscriber.sgml +++ b/doc/src/sgml/ref/pg_createsubscriber.sgml @@ -167,24 +167,31 @@ PostgreSQL documentation - - + + Remove all objects of the specified type from specified databases on the target server. - publications: The "all tables" publications established for this - subscriber are always removed; specifying this object type causes all - other publications replicated from the source server to be dropped as - well. + + + + publications: + The FOR ALL TABLES publications established for this + subscriber are always removed; specifying this object type causes all + other publications replicated from the source server to be dropped as + well. + + + - The objects selected to be dropped are individually logged and do show - up in a --dry-run. There is no opportunity to affect or stop the - dropping of the selected objects so consider taking a backup of them - using pg_dump. + The objects selected to be dropped are individually logged, including during + a . There is no opportunity to affect or stop the + dropping of the selected objects, so consider taking a backup of them + using pg_dump.