search

LucidDB / luciddb

DEFUNCT: See README
https://github.com/LucidDB/luciddb
Apache License 2.0
53 stars 24 forks source link

[LDB-202] Make auto deallocation a configuration option for LucidDB #120

Open dynamobi-build opened 12 years ago

dynamobi-build commented 12 years ago

[reporter="ngoodman", created="Tue, 27 Oct 2009 23:26:00 -0500 (GMT-05:00)"] Currently, in order to reclaim pages no longer referenced, ALTER SYSTEM DEALLOCATE OLD must be called.


Add a new system parameter, "autoDeallocate" that is set to true/false.


"False" makes no change to current behavior.


"True" changes the behavior as follows:
Any statement that could cause pages to be orphaned, and thus candidates for deallocation should trigger an automatic "deallocate old" call after their execution.

dynamobi-build commented 12 years ago

[author="jvs", created="Wed, 28 Oct 2009 00:00:56 -0500 (GMT-05:00)"] We might want to discriminate DDL vs DML here, since for a large database, this could make operations such as single-row inserts even more painfully slow than they are already.


So three levels (manual, auto-DDL, auto-all), with perhaps the default being auto-DDL to catch the common new user case of DROP TABLE/SCHEMA.