e2c0dd437a
..although it ought to work for other storage.KeyValueStore needs as
well. it's just optimized to work pretty well for a largish hierarchy of
paths.
This includes the addition of "long benchmarks" for KeyValueStore
testing. These will only be run when -test-bench-long is added to the
test flags. In these benchmarks, a large corpus of paths matching a
natural ("real-life") hierarchy is read from paths.data.gz (which you
can get from https://github.com/storj/path-test-corpus) and imported
into a particular KeyValueStore. Recursive and non-recursive queries are
run on it to detect performance problems that arise only at scale.
This also includes alternate implementation of the postgreskv client,
which works in a less-bizarre way for non-recursive queries, but suffers
from poor performance in tests such as the long benchmarks. Once this
alternate impl is committed to the tree, we can remove it again; I just
want it to be available for future reference.
10 lines
365 B
SQL
10 lines
365 B
SQL
DROP FUNCTION list_directory_reverse(BYTEA, BYTEA, BYTEA, INTEGER);
|
|
DROP FUNCTION list_directory(BYTEA, BYTEA, BYTEA, INTEGER);
|
|
DROP TYPE path_and_meta;
|
|
DROP FUNCTION component_increment(BYTEA, INTEGER);
|
|
DROP FUNCTION bytea_increment(BYTEA);
|
|
DROP FUNCTION truncate_after(BYTEA, INTEGER, INTEGER);
|
|
DROP VIEW pathdata_pretty;
|
|
DROP TABLE pathdata;
|
|
DROP TABLE buckets;
|