I am currently using the latest version of Liquibase for Redshift 4.7.1. In the logs with a level of FINE, I see that ‘SET search_path’ is being run by appending the --defaultSchemaName to the search_path of the cluster parameter group. When liquibase runs the SQL scripts, the schema is resolved to be the schema from the cluster parameter group, causing me to believe the search_path was reset. I found a similar issue on github that mentions the search_path being reset: Incorrect schema name in the search path is called when using the “–defaultSchemaName” on a non-default schema · Issue #1113 · liquibase/liquibase · GitHub
Is there still an issue happening on the liquibase side thats resetting the search_path?