0008439: Region maptiles - can previous tiles be removed from database as they are replaced by later versions

View Revisions: Issue #8439		[ All Revisions ] [ Back to Issue ]
Summary	0008439: Region maptiles - can previous tiles be removed from database as they are replaced by later versions

Revision	2019-01-01 10:51 by aiaustin
Description	Region maptiles are stored in the opensim.assets data table each time they are produced. But, as far as I understand, previous copies will never be used again. A good time to tidy the data base would seem to be at exactly the time that a new tile is stored, with older versions for that region UUID being deleted at that time. Note that at present I occasionally do the following mysql console command while the grid is stopped and sometimes thousands of these are deleted... even on a simple grid. DELETE FROM opensim.assets WHERE name LIKE "terrainImage_%";

Revision	2019-01-01 07:59 by aiaustin
Description	Region maptiles are stored in the opensim.assets data table each time they are produced. But, as far as I understand, previous copies will never be used again. A good time to tidy the data base would seem to be at exactly the time that a new tile is stored, wit older versions for that region UUID being deleted at that time. Note that at present I occasionally do the following mysql console command while the grid is stopped and sometimes thousands of these are deleted... even on a simple grid. DELETE FROM opensim.assets WHERE name LIKE "terrainImage_%";

Revision	2019-01-01 07:58 by aiaustin
Description	Region maptiles are stored in the opensim.assets data table each time theyar e produced. But, as far as I understand, previous copies will never be used again. A good time to tidy the data base would seem to be at exactly the time that a ew tile is stored. Note that at present I occasionally do the following mysql console command while the grid is stopped and sometimes thousands of these are deleted... even on a simple grid. DELETE FROM opensim.assets WHERE name LIKE "terrainImage_%";