Activity overview
Latest activity by robertcollins
From what you've shared, this is most likely expected behavior rather than a configuration issue. Flyway's clean command is designed to remove objects it manages, but foreign tables created through postgres_fdw aren't always handled the same way because they depend on external server definitions and object dependencies. If your migration process creates those foreign tables, you may need to explicitly drop them in a separate migration or pre-clean script before running clean . That's generally a safer approach than expecting Flyway to remove every dependency automatically. I usually think of it as any other clean up process. Whether you're cleaning up a database or dealing with something like mold clean up, it's important to understand what's connected to the underlying source before removing objects. Otherwise, you can end up with leftover dependencies or create new issues that are harder to troubleshoot later. One question: are the foreign tables created entirely by your migrations, or were they already present before Flyway started managing the database? That detail will help determine the best approach. / comments
From what you've shared, this is most likely expected behavior rather than a configuration issue. Flyway's clean command is designed to remove objects it manages, but foreign tables created through...