Re: Lock and read next
От | Ron Johnson |
---|---|
Тема | Re: Lock and read next |
Дата | |
Msg-id | 1062628639.7342.437.camel@haggis обсуждение исходный текст |
Ответ на | Lock and read next ("Girish Bajaj" <gbajaj@tietronix.com>) |
Ответы |
Re: Lock and read next
|
Список | 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.l.johnson@cox.net Jefferson, LA USA "Man, I'm pretty. Hoo Hah!" Johnny Bravo
В списке pgsql-novice по дате отправления: