Toronto, Canada - December 03, 2023 ## PostgreSQL pg_dbms_lock extension
This PostgreSQL extension provided compatibility with the DBMS_LOCK Oracle package except the `DBMS_LOCK.CONVERT()` function and some unsupported lock modes who anyway are rarely found in the Oracle PL/SQL stored procedures. The following stored procedures are implemented: * `ALLOCATE_UNIQUE()`: Allocates a unique lock ID to a named lock. * `REQUEST()`: Requests a lock of a specific mode. * `RELEASE()`: Releases a lock. * `SLEEP()`: Puts a procedure to sleep for a specific time. For instance, user locks can be used to do the following: * Provide exclusive access to an external device or service (like a printer). * Coordinate or synchronize parallelized applications. * Disable or enable execution of programs at specific times. * Detect whether a session has ended a transaction using COMMIT or ROLLBACK. This is the initial release of this exention. ## Links & Credits Any contribution to build a better tool is welcome. You can send your ideas, features requests or patches using the GitHub tools. **Links :** * Download: [https://github.com/hexacluster/pg_dbms_lock/releases/](https://github.com/hexacluster/pg_dbms_lock/releases/) * Support: use GitHub report tool at [https://github.com/hexacluster/pg_dbms_lock/issues](https://github.com/hexacluster/pg_dbms_lock/issues) * Documentation: [https://github.com/hexacluster/pg_dbms_lock#readme](https://github.com/hexacluster/pg_dbms_lock#readme) ## About pg_dbms_lock The pg_dbms_lock extension is an original work at [HexaCluster Corp](https://hexacluster.ai/), Gilles Darold and Akhil Reddy Banappagari are the authors and the official maintainers.
