New answers tagged vacuum
I'd suggest a key-value DBMS, but I throw this out there for interest's sake. Instead of performing INSERT & DELETE statements, only do UPDATEs. The table structure will be something like ID integer -- sequential ID Used boolean -- default FALSE Object -- whatever type is appropriate The object-holding column will be of fixed length to ...
According to postgresql documentation: VACUUM FULL actively compacts tables by writing a complete new version of the table file with no dead space. This minimizes the size of the table, but can take a long time. It also requires extra disk space for the new copy of the table, until the operation completes. So if you have one big table vacuum full ...
When the order of pages in the file has no relation to the order of pages on the disk, reordering the file does not make sense.
Top 50 recent answers are included