Alvaro Herrera wrote:
> Hi,
uhmmm patch?
>
> Here is the autovacuum patch I am currently working with. This is
> basically the same as the previous patch; I have tweaked the database
> list management so that after a change in databases (say a new database
> is created or a database is dropped), the list is recomputed to account
> for the change, keeping the ordering of the previous list.
>
> Modulo two low probability failure scenarios, I feel this patch is ready
> to be applied; I will do so on Friday unless there are objections.
>
> The failure scenarios are detailed in the comment pasted below. I
> intend to attack these problems next, but as the first one should be
> fairly low probability, I don't think it should bar the current patch
> from being applied. (The second problem, which seems to me to be the
> most serious, should be easily fixable by checking launch times and
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
