Moving the limitation back to pglogical_output based on Craig's feedback

umairshahid · umairshahid · commit 98d0d6580412 · 2016-01-04T22:13:31.000+05:00
diff --git a/README.md b/README.md
@@ -472,19 +472,6 @@ decoding plugin its self, such as:
 * Event triggers using DDL deparse to capture DDL changes as they happen and write them to a table to be replicated and applied on the other end; or
 * doing DDL management via tools that synchronise DDL on all nodes
 
-### Doesn't replicate global objects/shared catalog changes
-
-PostgreSQL has a number of object types that exist across all databases, stored
-in *shared catalogs*. These include:
-
-* Roles (users/groups)
-* Security labels on users and databases
-
-Such objects cannot be replicated by `pglogical_output`. They're managed with DDL that
-can't be captured within a single database and isn't decoded anyway.
-
-DDL for global object changes must be synchronized via some external means.
-
 ## How does pglogical differ from BDR?
 
 `pglogical` is based on technology developed for BDR and shares some code with
