| From: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
|---|---|
| To: | Carlos Benkendorf <carlosbenkendorf(at)yahoo(dot)com(dot)br>, Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Row level locking |
| Date: | 2005-10-12 13:30:50 |
| Message-ID: | 5.2.1.1.1.20051012212813.02c28558@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
will "lock sometable nowait" help?
http://developer.postgresql.org/docs/postgres/sql-lock.html
If it fails, something is in progress.
I believe there are also statement timeouts.
Regards,
Link.
At 11:56 AM 10/12/2005 +0000, Carlos Benkendorf wrote:
>We have applications that are sometimes locked by a long time application
>and I would like to avoid these by coding something to discover if the
>rows are locked before working with them.
>
>Both applications use only inserts in a table with a primary key.
>
>I´m sure that it is not the rigth approach, but I could not figure
>something better. Any suggestions?
>
>Benkendorf
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-10-12 13:43:39 | Re: problem with bit(n) type |
| Previous Message | Magnus Hagander | 2005-10-12 13:27:35 | Re: How to secure pgpass file from unauthorized reading of passwords ? (WIndows) |