How to Install and Uninstall python39-django-pglocks Package on openSuSE Tumbleweed
Last updated: December 27,2024
1. Install "python39-django-pglocks" package
This guide covers the steps necessary to install python39-django-pglocks on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python39-django-pglocks
Copied
2. Uninstall "python39-django-pglocks" package
Please follow the instructions below to uninstall python39-django-pglocks on openSuSE Tumbleweed:
$
sudo zypper remove
python39-django-pglocks
Copied
3. Information about the python39-django-pglocks package on openSuSE Tumbleweed
Information for package python39-django-pglocks:
------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python39-django-pglocks
Version : 1.0.4-1.16
Arch : noarch
Vendor : openSUSE
Installed Size : 10.6 KiB
Installed : No
Status : not installed
Source package : python-django-pglocks-1.0.4-1.16.src
Upstream URL : https://github.com/Xof/django-pglocks
Summary : PostgreSQL Advisory Locks for Django
Description :
django-pglocks provides a useful context manager to manage PostgreSQL advisory
locks. It requires Django (tested with 1.5), PostgreSQL, and (probably) psycopg2.
Advisory locks are application-level locks that are acquired and released purely
by the client of the database; PostgreSQL never acquires them on its own. They
are very useful as a way of signalling to other sessions that a higher-level
resource than a single row is in use, without having to lock an entire table or
some other structure.
It's entirely up to the application to correctly acquire the right lock.
Advisory locks are either session locks or transaction locks. A session lock is
held until the database session disconnects (or is reset); a transaction lock is
held until the transaction terminates.
Currently, the context manager only creates session locks, as the behavior of a
lock persisting after the context body has been exited is surprising, and
there's no way of releasing a transaction-scope advisory lock except to exit
the transaction.
------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python39-django-pglocks
Version : 1.0.4-1.16
Arch : noarch
Vendor : openSUSE
Installed Size : 10.6 KiB
Installed : No
Status : not installed
Source package : python-django-pglocks-1.0.4-1.16.src
Upstream URL : https://github.com/Xof/django-pglocks
Summary : PostgreSQL Advisory Locks for Django
Description :
django-pglocks provides a useful context manager to manage PostgreSQL advisory
locks. It requires Django (tested with 1.5), PostgreSQL, and (probably) psycopg2.
Advisory locks are application-level locks that are acquired and released purely
by the client of the database; PostgreSQL never acquires them on its own. They
are very useful as a way of signalling to other sessions that a higher-level
resource than a single row is in use, without having to lock an entire table or
some other structure.
It's entirely up to the application to correctly acquire the right lock.
Advisory locks are either session locks or transaction locks. A session lock is
held until the database session disconnects (or is reset); a transaction lock is
held until the transaction terminates.
Currently, the context manager only creates session locks, as the behavior of a
lock persisting after the context body has been exited is surprising, and
there's no way of releasing a transaction-scope advisory lock except to exit
the transaction.