Timeline for Why can MySQL handle multiple updates concurrently and PostgreSQL can't?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2022 at 22:08 | comment | added | SDReyes | I'm a bit late to this, but this was the answer. postgres was slower than mysql in this case and there are tradeoffs everywhere. I'm still a postgres fan, but now i know this is the price we pay for cool mvcc concurrency | |
| Apr 8, 2022 at 22:07 | vote | accept | SDReyes | ||
| Oct 11, 2016 at 22:35 | comment | added | user1822 |
You might want to add, that you can combine the select with an update using a writeable CTE: with to_update (select ... ) update positions set updated_at = now() where id in (select id from to_update). Especially with an "expensive" where clause this is probably faster then evaluating the where condition again in the update statement.
|
|
| Oct 11, 2016 at 22:31 | history | answered | András Váczi | CC BY-SA 3.0 |