This section assumes that you have successfully completed the getting
started guide and reviewed the
Logical Replication Operational
Guide.
Schema Changes
PostgreSQL logical replication copies row changes, not DDL. That means schema changes on the publisher are not applied automatically on ParadeDB. Keep these rules in mind:- Existing replicated tables must stay schema-compatible on both sides
- New tables must exist on ParadeDB before they can replicate there
- BM25 indexes are local to ParadeDB and must be created or rebuilt there
- Publication membership still controls whether a new table is replicated at all
FOR ALL TABLES include new
tables automatically, and publications created with FOR TABLES IN SCHEMA ...
include new tables created in those schemas automatically. If your publication
was created from an explicit table list, new tables will not replicate until
you add them manually. If you do not want a table replicated to ParadeDB, leave
it out of the publication.
For the full sequence for adding a replicated searchable table, see Add New
Tables.