Please notice that Pyrit used to create an index on a table in an unprofitable column-order. This causes a full table scan for operations like “eval” and “delete_essid” which may take a very long time for large (hundreds of millions of entries) databases.
This problem is about to get fixed for 0.3.1-svn so Pyrit creates new databases with their indexes in in proper column-order. Older databases can be fixed by creating a new index like this (use the database-server’s sql-console):
CREATE INDEX myrescueidx ON results (essid_id, _key);
People using the on-disk (“file://”) storage backend are not affected.
Leave a comment
No comments yet.