[6.x] Fixed breaking compatability with multi-schema postgres #30555
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Postgres engine supports a multi-schema search path, and parts of the PostgresBuilder do not.
This PR addresses multiple schema support in a non-breaking way for 6.x.
Furthermore, to give more granular control, I allowed the $excludedTables portion of the dropAllTables() method to be set via configuration values, while gracefully falling back to the original value.
This level of granularity is particularly important when it comes to postgresql extensions and the tables they sometimes create.