Timeline for Very slow DELETE in PostgreSQL, workaround?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2023 at 10:39 | answer | added | Gema Pena Chimeno | timeline score: 0 | |
| Dec 31, 2020 at 18:35 | answer | added | marcel | timeline score: 3 | |
| Dec 2, 2019 at 1:57 | answer | added | blindguy | timeline score: 2 | |
| Jan 7, 2019 at 8:52 | answer | added | Mikko Rantalainen | timeline score: 62 | |
| Aug 4, 2018 at 4:53 | comment | added | jd. | After 5 years, I'm changing the accepted answer. Slow DELETEs are almost always caused by missing indexes on foreign keys that directly or indirectly reference the table being deleted from. Triggers that fire on DELETE statements can slow things down too, although the solution is almost always to make them run faster (e.g. by adding missing indexes) and almost never to disable all triggers. | |
| Aug 4, 2018 at 4:51 | vote | accept | jd. | ||
| Feb 13, 2018 at 22:28 | history | edited | András Váczi | CC BY-SA 3.0 |
added 73 characters in body
|
| Sep 7, 2017 at 9:57 | answer | added | Johann8 | timeline score: 19 | |
| May 11, 2016 at 20:53 | answer | added | ailnlv | timeline score: 127 | |
| May 16, 2015 at 1:22 | history | tweeted | twitter.com/#!/StackDBAs/status/599384337461747712 | ||
| Mar 20, 2013 at 14:15 | vote | accept | jd. | ||
| Aug 4, 2018 at 4:51 | |||||
| Mar 20, 2013 at 10:01 | answer | added | Chris Travers | timeline score: 55 | |
| Mar 19, 2013 at 17:01 | review | First posts | |||
| Mar 19, 2013 at 17:20 | |||||
| Mar 19, 2013 at 16:48 | history | edited | András Váczi |
retag
|
|
| Mar 19, 2013 at 16:44 | history | asked | jd. | CC BY-SA 3.0 |