Unnecessary snapshot on liquibase update


From http://forum.liquibase.org/topic/update-with-lots-of-already-executed-changesets-incredibly-slow-liquibase-3-0-2-oracle-10g#49382000000827004

I'm using liquibase 3.0.2 to update an Oracle 10g database. There are about 1300 changesets in the xml file. The first time it runs normal. No performance problems. When I run the same file again it takes a very long time to finish. The only thing it should have to do is check if the changeset has been executed and compare the checksums as far as I know.

When I monitor the database I see that all the columns of all the tables are being checked (SELECT <columnname> FROM <tablename> WHERE 0=1). With almost 1300 tables this takes quite a long time. I see no reason for doing this since there are no preconditions in the xml file at all. Anyone know if there's a specific reason for doing this or is this a bug?


Oracle (probably others)


Nathan Voxland
September 23, 2013, 9:38 PM

Fixed in 3.0.5

Your pinned fields
Click on the next to a field label to start pinning.


Nathan Voxland