Timeline for PostgreSQL - 30000 row updates, setting non-indexed boolean column to 'true' takes hours
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 18, 2023 at 9:07 | comment | added | bobflux | Well the plan in your question is good, so it has to be something else | |
| Dec 18, 2023 at 5:17 | comment | added | Justin Lowen | You're right. The queries written in my answer are different from my original question. It looks like the actual problem with the queries I was grappling with was that the cross join was not obvious (someone did not understand how to alias the updated table ("AS") , and instead joined it to itself unnecessarily). I am not sure why the revised query in my original question was taking so long to update as I had rewritten the query which incidentally fixed the cross join problem. I think most likely an issue with disk speed or bloated table for the original queryas others have suggested. | |
| Dec 15, 2023 at 11:50 | comment | added | bobflux | The first one has an implicit cross join because it contains two instances of "resources" table. This is not the same problem as the query in the question. | |
| S Dec 14, 2023 at 21:56 | review | First answers | |||
| Dec 14, 2023 at 22:36 | |||||
| S Dec 14, 2023 at 21:56 | history | answered | Justin Lowen | CC BY-SA 4.0 |