From: | "Knut Aksel Rysland" <knutroy(at)ifi(dot)uio(dot)no> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Non-blocking LOCK |
Date: | 2000-06-27 17:56:29 |
Message-ID: | 200006271756.29991.ganglot@ifi.uio.no |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi.
How can I request a lock in a non-blocking way? Instead of blocking
until a certain lock can be acquired, I would like my client
applications to give up immediately when a conflicting lock exists.
My wish is that client applications locks the data while it is being
edited, thus making the locks possibly long-lived. Subsequent update
requests to the same data, will then be rejected immediately. I am
hoping to find a server-side solution to this problem, so that rude
clients are unable to circumvent the lock.
Is the "user_locks" module (which "provides support for user-level
long-term cooperative locks") the best approach? It appears that this
solution requires well-behaving clients. Do I have other choices?
Sincerely,
Knut Aksel Rysland
From | Date | Subject | |
---|---|---|---|
Next Message | Bryan White | 2000-06-27 18:03:00 | Re: puzzled by the docs |
Previous Message | Karl F. Larsen | 2000-06-27 16:47:14 | Re: puzzled by the docs |