On 24-10-2011 11:36, Tom Lane wrote:
Euler Taveira de Oliveira<eu...@timbira.com> writes:
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.
I'm not terribly thrilled with that because (a) large objects seem like
mostly a legacy feature from here, and
>
Right, but there isn't a solution for > 1 GB column data besides LO.
(b) it's hard to see how to
implement it without imposing overhead on everybody, whether they use
LOs or not. This is especially problematic if you're proposing that
cleanup triggers not be required.
I was thinking about starting the LO cleanup after autovacuum finishes the
VACUUM command (so no trigger, no new mechanism). And about the overhead
imposed, it will only execute the cleanup code in the tables that have oid/lo
columns (this information will be collected when the autovacuum collects table
information).
--
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
