Hello Social discuss, I recently inherited a gnusocial instance and just upgraded it from 1.1.x to the current master branch. I'd like to extend kudos to whomever wrote upgrade.php; it was very tolerant of being killed and restarted, which is an extremely nice property for a database upgrade script.
I've noticed that our queue_item table has a lot of rows where `claimed` is not NULL, and the claim date is long in the past. I've included a set of query output (below) to illustrate this. Is it safe to delete these rows? Or to put it a different way, what's the appropriate way to tell gnusocial "these are old -- just forget about them". (I went through the scripts/ directory, but didn't see anything to the effect of "clean up old queue items"). Steve -- old queue_items querymysql> select year(claimed) y, month(claimed) m, count(*) from queue_item
where claimed is not null
group by y, m
order by y,m;
+------+------+----------+
| y | m | count(*) |
+------+------+----------+
| 2014 | 8 | 74 |
| 2014 | 9 | 70 |
| 2014 | 10 | 53 |
| 2014 | 11 | 77 |
| 2014 | 12 | 112 |
| 2015 | 1 | 273 |
| 2015 | 2 | 108 |
| 2015 | 3 | 43 |
| 2015 | 4 | 32 |
| 2015 | 5 | 38 |
| 2015 | 6 | 48 |
| 2015 | 7 | 63 |
| 2015 | 8 | 205 |
| 2015 | 9 | 87 |
| 2015 | 10 | 59 |
| 2015 | 11 | 39 |
| 2015 | 12 | 58 |
| 2016 | 1 | 54 |
| 2016 | 2 | 120 |
| 2016 | 3 | 5667 |
| 2016 | 4 | 3083 |
| 2016 | 5 | 2660 |
| 2016 | 6 | 2105 |
| 2016 | 7 | 3047 |
| 2016 | 8 | 1626 |
| 2016 | 9 | 20 |
| 2016 | 10 | 3 |
| 2016 | 11 | 1188 |
| 2016 | 12 | 5 |
| 2017 | 1 | 24 |
| 2017 | 2 | 20 |
| 2017 | 4 | 55 |
| 2017 | 5 | 33 |
| 2017 | 6 | 35 |
| 2017 | 7 | 15 |
| 2017 | 9 | 1 |
+------+------+----------+
signature.asc
Description: Digital signature
