improve performance of databasechangelog updates?

[tooptoop4]

if i have a sql changeset file with 600 different changesets and then add 601st changeset i notice a lot of individual UPDATE sqls (looks like 1 per changeset to update latest time for the hash) are running against the internal liquibase databasechangelog table (in redshift,) if each one takes 300ms then the time adds up. for redshift can these updates be batched up into 1 update?

[tooptoop4]

what do u think @filipelautert @wwillard7800 ?

[filipelautert]

@tooptoop4 right now there is no way to batch them. But it should only happen if you are upgrading from a version before 4.22 to any other after that - and only once. Is that your case?

[tooptoop4]

with no version upgrade, just a new changeset added to .sql file its going through and doing update on all rows