From: | Germán Poó Caamaño <gpoo(at)ubiobio(dot)cl> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | GSoC's possible project |
Date: | 2007-03-21 02:26:22 |
Message-ID: | 1174443982.8054.50.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-03-21 02:36:57 | Re: CREATE INDEX and HOT - revised design |
Previous Message | Bruce Momjian | 2007-03-21 01:29:30 | Caught up on email |