Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add implementation with advisory(session) lock #28

Closed
nkonev opened this issue Feb 6, 2023 · 2 comments
Closed

Add implementation with advisory(session) lock #28

nkonev opened this issue Feb 6, 2023 · 2 comments

Comments

@nkonev
Copy link
Owner

nkonev commented Feb 6, 2023

See https://github.com/blagerweij/liquibase-sessionlock

@nkonev nkonev added this to the V3.x milestone Feb 6, 2023
@nkonev
Copy link
Owner Author

nkonev commented Mar 25, 2023

Upd:

Starting from 2.9.0 so-called database-specific lock was implemented.
It is advisory lock in case PostgreSQL, session lock in case MySQL and MariaDB. For other databases it is (still) usual table-based lock.
This means, if you migrating from 2.8.x in case before mentioned databases you can remove your lock table by

drop table migrations_lock;

If you want to preserve old behavior - you can set

r2dbc:
  migrate:
    prefer-db-specific-lock: false

@nkonev
Copy link
Owner Author

nkonev commented Apr 1, 2023

SQL Server and H2 aren't seen very popular, leaving them with table locking for now, session lock can be implemented in the future or by demand.

@nkonev nkonev closed this as completed Apr 1, 2023
@nkonev nkonev removed this from the V4.x milestone Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant