From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | PgSQL Novice ML <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Lock and read next |
Date: | 2003-09-03 22:37:19 |
Message-ID: | 1062628639.7342.437.camel@haggis |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Wed, 2003-09-03 at 16:56, Girish Bajaj wrote:
> Is there a way if one transaction has locked a row in a table, the
> next transaction does not get blocked while reading the same row, but
> moves on to the next record in the table to read?
>
> Example:
>
> Transaction 1
>
> Select * from table LIMIT 1 FOR UPDATE
>
> --transaction takes 3 min to complete
Why the heck do the transactions take 3 minutes??!!??!!
> Transaction 2
>
> Select * from table LIMIT 1 FOR UPDATE
>
> Here, transaction 2 blocks on the same record that transaction 1 has a
> write lock on (for 3 min). Is there a way to tell transaction 2 to
> move on and get the next writable record?
Does SQL even support that kind of semantics?
--
-----------------------------------------------------------------
Ron Johnson, Jr. ron(dot)l(dot)johnson(at)cox(dot)net
Jefferson, LA USA
"Man, I'm pretty. Hoo Hah!"
Johnny Bravo
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Eckermann | 2003-09-03 22:55:32 | Re: Modyifying a column's datatype |
Previous Message | Stephan Szabo | 2003-09-03 22:15:27 | Re: Modyifying a column's datatype |