While marking up TODO for potential new-hacker items I've run across
some items that probably need more explanation:
o Allow commenting of variables in postgresql.conf to restore them to defaults
This doesn't work already?
* Allow triggers to be disabled [trigger]
Isn't this going to be in 8.1?
* SQL*Net listener that makes PostgreSQL appear as an Oracle database to clients
Any reason not to do this for other databases; notably MySQL?
o Do VACUUM FULL if table is nearly empty?
Since that results in an exclusive table lock (which is vastly different
from regular vacuum), wouldn't it be better to just throw a warning?
* Reduce WAL traffic so only modified values are written rather than entire rows?
Shouldn't this be marked as depending on eliminate need to write full
pages? (At least ISTM it won't do any good as long as we're writing full
pages)
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com 512-569-9461