Re: Deadlock with ShareLocks?
От | Mario Weilguni |
---|---|
Тема | Re: Deadlock with ShareLocks? |
Дата | |
Msg-id | 200512131657.54984.mweilguni@sime.com обсуждение исходный текст |
Ответ на | Re: Deadlock with ShareLocks? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Deadlock with ShareLocks?
|
Список | pgsql-hackers |
Am Dienstag, 13. Dezember 2005 16:52 schrieb Tom Lane: > Mario Weilguni <mweilguni@sime.com> writes: > > Since the type field is PK, there cannot be 2 rows with type='list', I > > guess the deadlock must have some different explanation. > > Then the deadlock must involve rows in two different tables. What else > are you doing in the same transaction(s) as updating last_modified? That's what I think too, unfortunatly, I can't say for sure. The application uses around 1000 different queries, and I had no logging on for this case. So I guess two backends might have issued interleaved updates. I think without logging this cannot be solved here. Best regards,Mario Weilguni
В списке pgsql-hackers по дате отправления: