Hi,
The main point of autovacuum is maintenance tasks. Currently, it executes
VACUUM and ANALYZE commands. I want to propose that we incorporate vacuumlo
functionality into it. While dealing with large objects (LO), we have lo
contrib module that helps with LO maintenance but has some limitations (does
not handle DROP TABLE and TRUNCATE cases) and vacuumlo that does an excellent
job but have to be executed outside DBMS. The proposal is to clean up LO when
autovacuum triggers VACUUM; cleanup LO routine will starts after(?) VACUUM
command.
In a near future I want to propose that orphaned LO be cleaned up by VACUUM
but that a history for another thread...
Comments?
--
Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
