- 
                Notifications
    
You must be signed in to change notification settings  - Fork 88
 
Add acquire timeout support to PostgreSQLMutex #80
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 acquire timeout support to PostgreSQLMutex #80
Conversation
0204814    to
    a9f8890      
    Compare
  
    4143853    to
    7ee091e      
    Compare
  
    | 
           @mvorisek just following up on this one, please let me know if you need anything else.  | 
    
| 
           Done, had to transfer the fork out of our org for the option to become available.  | 
    
| 
           The coverage discovered there is no test for the lock acquired. Please add E2E test. To   | 
    
| 
           Do you want two mutex factories in   | 
    
| 
           Yes and thank you, great contribution ❤  | 
    
| 
           @mvorisek thanks for making it happen 🙏  | 
    

closes #66
Add support for timeouts to PostgresSQLMutex, as mentioned in this issue #66 PostgreSQL supports a non-blocking advisory lock function.
We've needed this a few times and previously I've rolled our own lock/mutex but it'd be easier if it was in the package. Happy to work through any feedback on this one, tried to follow existing patterns, if I missed anything let me know.