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

Remove Sqlg's topology lock. #330

Closed
pietermartin opened this issue Feb 6, 2019 · 1 comment
Closed

Remove Sqlg's topology lock. #330

pietermartin opened this issue Feb 6, 2019 · 1 comment
Assignees

Comments

@pietermartin
Copy link
Owner

This ticket arose out of #329

Look at removing all locks from Sqlg and let postgres throw dead lock exceptions rather.

Removing the topology lock needs careful thought and testing as it puts the burden on the client to retry failed transaction due to postgres dead lock exceptions.
This will also most likely break existing applications so maybe make it optional to use Sqlg's locks or not.

@pietermartin
Copy link
Owner Author

To clarify the burden on the client. During concurrent schema creation the database will throw exceptions. In postgresql it is table already exist or similar exceptions. In this case the client will have to rollback and retry the transaction.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant