Setting tiling layouts/indexes needs testing

[Dimitar Misev]

Several combinations of tiling layouts and indexes seem to be broken (see this paper for details).

This should be thoroughly tested and fixed.

[Dimitar Misev]

There's a problem with data somehow leaking in the database.

I initialized a 3D object of type octet with AlignedTiling, tile configuration "[0:399,0:99,0:99];4000000"

The domain is 0:458,0:1120,0:1120, so around 500MB. Each timeslice was a separate TIFF file, inserted via a partial update.

In the end the database grew from 0 to 23GB, and deleting the collection with rasql left the database still at 23GB.. so the only way to get rid of all that is dropdb RASBASE

This doesn't happen with the default regular tiling, but then the query takes 30x longer to evaluate.

A tile configuration [0:49,0:244,0:244];3251250 results in a 3GB database.

[Dimitar Misev]

I've further tested this with the jacobs campus data, which is of size 14995 x 9996 x 3 = 449670060 bytes or 429MB.

Importing into rasdaman with rasimport, increased the postgres DB by only 245MB (??)

Repeating drop/insert a few times consistently increases the db on disk by 245MB (the drop doesn't change the size). Before each drop/insert I restart postgres.

[Dimitar Misev]

Depends on #246

[Dimitar Misev]

Done in

commit a431e972619109661551cdc6afb865f4afff5619
Author: Dimitar Misev <misev@rasdaman.com>
Date:   Mon Dec 17 00:53:34 2012 +0100

    Fix R+ tree index to allow inserting multiple tiles, and directional tiling (ticket 161)