Takes 1-2 minutes in the netarkivet PROD environment using NetarchiveSuite 4.0 and postgreSQL as database

Workaround: save a bookmark directly to the filestatus page:
http://kb-prod-adm-001.kb.dk:8080/BitPreservation/Bitpreservation-filestatus.jsp

As a workaround, one can bookmark the direct links to checksum/filestatus e.g. for PLIGT:

Well that query would required some post processing since file_status count must be aggregated over the different checksum states. But only one table scan is used so that is better in that sense.

Anyway that query should never be called from the front-end only as a trigger to bitrepo status replies in some back-end thread.

My index didn't do anything at all for the performance and neither did clustering the table. And it's only wannabe clustering since it is not maintained so you have to run the cluster command regularly to re-cluster the table. Pure madness.

Why not just keep using derby for the adminDB?
Otherwise there will no be release today!