Timeline for django_session table killing my MySQL server and django app
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 5, 2019 at 3:50 | vote | accept | uberrebu | ||
Mar 5, 2019 at 3:48 | history | edited | uberrebu | CC BY-SA 4.0 |
added 2093 characters in body
|
Mar 4, 2019 at 5:59 | history | edited | uberrebu | CC BY-SA 4.0 |
added 20 characters in body
|
Mar 4, 2019 at 5:45 | history | edited | uberrebu | CC BY-SA 4.0 |
added 336 characters in body
|
Mar 2, 2019 at 20:49 | comment | added | uberrebu | i have updated question with output of the SQL commands at bottom of the post/question | |
Mar 2, 2019 at 20:46 | history | edited | uberrebu | CC BY-SA 4.0 |
added 304 characters in body
|
Mar 2, 2019 at 0:15 | comment | added | Wilson Hauck | Please post TEXT data requested by danblack on Feb 25, 19 at 22:04 plus results of SHOW INDEX FROM django_session; Thanks | |
Feb 25, 2019 at 22:32 | answer | added | danblack | timeline score: 2 | |
Feb 25, 2019 at 22:04 | comment | added | danblack |
The problem is that SELECT COUNT(*) FROM django_session WHERE django_session.last_login >= '2019-02-23 13:00:37' is a slow query. Please show EXPLAIN SELECT COUNT(*) FROM django_session WHERE django_session.last_login >= '2019-02-23 13:00:37' and SHOW CREATE TABLE django_session
|
|
Feb 25, 2019 at 21:41 | history | asked | uberrebu | CC BY-SA 4.0 |