Joe Lester <joe_lester@xxxxxxxxxxxxxx> writes: > Is there a recommended "postgres way" to determine if a certain row is > locked... without blocking? 8.1 has a SELECT FOR UPDATE NOWAIT option. Alternatively, just do a wait while having a very short statement_timeout. > In my custom postgres client app I'd like to be able to determine if > another user is "modifying" a given record. If so, I would present a > dialog to the user such as "Record Locked. Sam Smith is already > modifying this record. Try again later." However, I think the question is moot because it's predicated on a terrible underlying approach. You should NEVER design a DB app to hold a lock while some user is editing a record (and answering the phone, going out to lunch, etc). Fetch the data and then let the user edit it while you are not in a transaction. When he clicks UPDATE, do BEGIN; SELECT the row FOR UPDATE; check for any changes since you fetched the data originally if none, UPDATE and commit else rollback and tell user about it If you do see conflicting changes, then you have enough info to resolve the conflicts or abandon the update. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
