[Postgres target] Schema drop not being replicated to the target

[eminano]

Describe the bug
Drop schema queries are not replicated in the postgres target.

To Reproduce
Steps to reproduce the behavior:

1. Create a schema CREATE SCHEMA test
2. Create a table in the schema CREATE TABLE test.test(id serial primary key, name text)
3. Run pgstream with replication
4. Validate schema and table are created in the target
5. Drop schema on the source database DROP SCHEMA test CASCADE
6. Schema not being dropped in the target

Expected behavior
Schema should be dropped in the target when it's dropped in the source database.

Screenshots
If applicable, add screenshots to help explain your problem.

Setup (please complete the following information):

• pgstream version: v0.9.3
• Postgres version: 17.6
• Postgres environment: self-hosted

[dosubot]

Pgstream is designed to replicate schema drops (DROP SCHEMA) by logging DDL changes via event triggers into the pgstream.schema_log table, which are then processed and applied on the target. If schema drops are not being replicated, the most common causes are configuration issues. Make sure your target Postgres config includes apply_schema_changes: true, schema_log_store_url pointing to the source database, and the injector modifier enabled. Without these, schema changes—including drops—will not be applied on the target. Also, ensure the pgstream.schema_log table is not excluded from replication and that the event triggers are present and firing on the source database.

There are known issues in v0.9.3 where schema changes may not replicate live if the configuration is incomplete or if certain snapshot modes are used. The mechanism for DROP SCHEMA replication exists and should work if configured properly. For more details, see this architecture explanation, event trigger implementation, and configuration troubleshooting.

If you’ve confirmed your config and triggers are correct but still see issues, check for errors in the logs related to schema log acknowledgment or DDL event processing, as these can indicate deeper bugs or environmental problems.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}