Assess logs to understand changelog efficiency

Last updated: September 2, 2025

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

1

Run the --log-level=INFO command

Once you know what is slowing down your update, try to alter just those changesets rather than throwing out the whole changelog and starting from scratch. You will still want to retest your changelog in-depth, but it is a far less risky change.

2

Run the --log-level=DEBUG command

Once you know what is slowing down your update, try to alter just those changesets rather than throwing out the whole changelog and starting from scratch. You will still want to retest your changelog in-depth, but it is a far less risky change.