npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

distributed-locks-postgresql

v1.0.3

Published

The postgresql package for the storage layer for distributed locks

Downloads

4

Readme

Postgresql Algorithm for lock guarantees

Start

We create a table for locks if it doesn't exist, table name is customizable

CREATE TABLE IF NOT EXISTS table } (
    key varchar(50),
    value varchar(100) NOT NULL,
    ttl integer NOT NULL,
    obtained_at timestamp DEFAULT current_timestamp,
    CONSTRAINT pk_index PRIMARY KEY (key)
);

Acquiring Lock

We start a transaction with isolation level repeatable read and it only has one SQL statement that inserts the row representing the lock

INSERT INTO table (key, value, ttl, obtained_at)
VALUES ('key', 'lock-value', 10, current_timestamp)
ON CONFLICT ON CONSTRAINT pk_index
DO
    UPDATE SET value = 'lock-value', ttl = 10
    WHERE locks.obtained_at + interval '1' second * locks.ttl  < current_timestamp
returning *

Using the key that represents the critical section as primary key, we try to insert a record with it and the value represents our lock, if there is a conflict on the primary key constraint (someone else was able to acquire the lock) we can still update that row only if the previous lock expired (it's ttl + obtained at < current time stamp>).

If the upsert operation was successful we return a truthy value

Releasing Lock

Same as acquiring a lock we use a transaction with isolation level repeatable read. Simply delete the row with key equal to the critical section value, and the value equal to the lock value

DELETE FROM table
where key = 'key' AND value = 'lock-value';