Skip site navigation (1) Skip section navigation (2)

Re: Can pessimistic locking be emulated?

From: Christoph Haller <ch(at)rodos(dot)fzk(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Cc: merlin(dot)moncure(at)rcsonline(dot)com, josh(at)agliodbs(dot)com
Subject: Re: Can pessimistic locking be emulated?
Date: 2003-02-28 09:04:55
Message-ID: 3E5F2637.F65622F@rodos.fzk.de (view raw or flat)
Thread:
Lists: pgsql-hackers
>
> Just as a suggestion:  In most of my applications, we have a security
layer
> which is implemented through server-side functions.  These functions
keep a
> table updated which contains:
>
> lock_table
> record_id
> lock_user
> time_locked
That's an excellent and even portable idea.
>
> This allows us to avoid nasty "your update cannot be processed"-type
error
> messages by showing the user up front which records are locked, as
well as
> allowing the admin to decide when locks should "time out".
>
> I tend to find in general that database locking mechanisms are a very
poor
> locking strategy for a good UI.
>
True. But you circumvented it elegantly.

Regards, Christoph



Responses

pgsql-hackers by date

Next:From: Andreas SchmitzDate: 2003-02-28 09:16:29
Subject: Re: Still a bug in the VACUUM ??? !!!
Previous:From: Christopher Kings-LynneDate: 2003-02-28 07:50:21
Subject: Are my emails getting through at all???

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group