wiz
wiz
TRUNCATE'ing the hashrates and difficulty adjustments is just a re-index, just move those to their own new migrations and it will be fine
Will merge after manually bumping prod servers to 81 to avoid the re-indexing downtime
the accelerate button should always appear, this is the actual bug
@knorrium isn't this old PR fixing your thing
``` root@localhost [mempool]> select added, vsize_1 from statistics order by added desc limit 200; +---------------------+----------+ | added | vsize_1 | +---------------------+----------+ ... | 2023-03-04 05:43:35 | 38492371 | | 2023-03-04...
I think it's fine for prod now that we are using redis but it might still reproduce using disk cache for community nodes on RPI devices?
how about redis?
@junderw can you please work on this
does this require a re-index?
ok then please rebase