Re: Autovacuum in the backend - Mailing list pgsql-hackers

From Matthew T. O'Connor
Subject Re: Autovacuum in the backend
Date
Msg-id 42B106D9.1000405@zeut.net
Whole thread Raw
In response to Re: Autovacuum in the backend  (Neil Conway <neilc@samurai.com>)
List pgsql-hackers
Neil Conway wrote:

> Alvaro Herrera wrote:
>
>> One issue I do have to deal with right now is how many autovacuum
>> processes do we want to be running.  The current approach is to have one
>> autovacuum process.  Two possible options would be to have one per
>> database, and one per tablespace.  What do people think?
>
>
> Why do we need more than one pg_autovacuum process? (Note that this 
> need not necessarily imply only one concurrent VACUUM, as you can use 
> non-blocking connections in libpq.) 


Part of the backend integration work Alvaro is doing is teaching 
autovacuum to do it's work without libpq.




pgsql-hackers by date:

Previous
From: "Matthew T. O'Connor"
Date:
Subject: Re: Autovacuum in the backend
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: [GENERAL] INHERITS and planning