I'm a student and I'm planning to submit a project for Google Summer of Code. I would like to receive feedback about to implement the vacumm scheduling in order to allow maintenance's windows.
I have read the whole discussion about "Autovacuum improvements"[1] taken in January. Alvaro Herrera suggested two improvements, (probably following an idea of Matthew T. O'Connor), which were: - Scheduling (a maintenance window) - Process Handling. As fas as I know, the process handling is a work in progress[2], while the scheduling is defined (almost complete) but not implemented yet. Which is not clear to me (yet), if it would required collecting enough information through implementing a sort of 'VACUUM SUMMARY'[3]. I would like to receive opinions or suggestions about picking this task. I haven't explained in more detail what is this scheduling, because I think, it was clear enough, as far as I understood, in the thread. Thanks in advance, [1] http://archives.postgresql.org/pgsql-hackers/2007-01/msg00684.php [2] http://archives.postgresql.org/pgsql-hackers/2007-03/msg00639.php [3] http://archives.postgresql.org/pgsql-hackers/2005-07/msg00409.php -- Germán Poó Caamaño Concepción - Chile ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
