Timeline for `ON CONFLICT DO UPDATE` causing deadlocks?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 26, 2016 at 19:07 | vote | accept | Fake Name | ||
| Apr 25, 2016 at 17:38 | comment | added | Fake Name | @ypercubeᵀᴹ - I figured it was unneeded, but I was having issues with what I thought was the update being applied to too many rows (all of them) earlier, so I added some precautionary stuff. | |
| Apr 25, 2016 at 4:51 | comment | added | ypercubeᵀᴹ |
No woriies. Thnx for editing. By the way, the AND web_pages.url = EXCLUDED.url is not needed I think, since the conflict is on (url). I don't suppose that that would make any difference for the deadlocks.
|
|
| Apr 24, 2016 at 22:34 | history | edited | Fake Name | CC BY-SA 3.0 |
edited body
|
| Apr 24, 2016 at 22:34 | comment | added | Fake Name |
@ypercubeᵀᴹ - Whoops. I originally had the question written as being at the SERIALIZABLE isolation level, and then later realized the logs were from the REPEATABLE READ level, made some changes, and missed fixing that.
|
|
| Apr 24, 2016 at 10:31 | answer | added | Jobin Augustine | timeline score: 5 | |
| Apr 24, 2016 at 7:58 | history | asked | Fake Name | CC BY-SA 3.0 |