You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Sometimes it makes sense to set up the replication set (i.e. tables to be replicated) inside the database rather than via the configuration file. Or provide a two-level customization, with tables explicitly included at the database level and excluded using the configuration wildcards.
For that purpose, CREATE TABLE and ALTER TABLE commands are extended with the optional {ENABLE | DISABLE} PUBLICATION clause. Also ALTER DATABASE command is extended with batch operations to manage the replication set:
ALTER DATABASE ADD {ALL | TABLE <comma-separated table list>} TO PUBLICATION
ALTER DATABASE DROP {ALL | TABLE <comma-separated table list>} FROM PUBLICATION
And finally, ALTER DATABASE command now offers an ability to switch the replication ON/OFF at runtime:
ALTER DATABASE {ENABLE | DISABLE} PUBLICATION
See also /doc/replication.md and /doc/sql.extensions/README.ddl.txt.
The text was updated successfully, but these errors were encountered:
Submitted by: @dyemanov
Sometimes it makes sense to set up the replication set (i.e. tables to be replicated) inside the database rather than via the configuration file. Or provide a two-level customization, with tables explicitly included at the database level and excluded using the configuration wildcards.
For that purpose, CREATE TABLE and ALTER TABLE commands are extended with the optional {ENABLE | DISABLE} PUBLICATION clause. Also ALTER DATABASE command is extended with batch operations to manage the replication set:
ALTER DATABASE ADD {ALL | TABLE <comma-separated table list>} TO PUBLICATION
ALTER DATABASE DROP {ALL | TABLE <comma-separated table list>} FROM PUBLICATION
And finally, ALTER DATABASE command now offers an ability to switch the replication ON/OFF at runtime:
ALTER DATABASE {ENABLE | DISABLE} PUBLICATION
See also /doc/replication.md and /doc/sql.extensions/README.ddl.txt.
The text was updated successfully, but these errors were encountered: