Assess logs to understand changelog efficiency
Sometimes liquibase update takes too long, which can indicate that th changelog may need to be trimmed. Liquibase tries to be as efficient as possible when comparing the contents of the DATABASECHANGELOG table with the current changelog file and even if there are thousands of already ran changesets, an update command should take just seconds to run. If you find that update takes longer than it should, watch the Liquibase log to determine why.
Assess logs to understand changelog efficiency
Run the --log-level=INFO command
Perhaps there is an old runAlways="true" changeset that no longer needs to run or there are preconditions which are no longer needed. Running this step allows you to assess what is slowing down the update command.
Run the --log-level=DEBUG command
Perhaps there is an old runAlways="true" changeset that no longer needs to run or there are preconditions which are no longer needed. Running this step allows you to assess what is slowing down the update command.