Hi, Peter,
> How is this different from what autovacuum does?
My application needs to do vacuum by itself, while
autovacuum does it as daemon.
The database is updated so frequently that
normal vacuum costs too much and tables to be updated are
not so many as the whole database is vacuumed.
I want to use autovacuum except the feature of daemon,
but want to control when to vacuum and which table to vacuum.
So, nothing is different between autovacuum and smartvacuum(),
but former is daemon and later is user function.
c.f. I ran autovacuum before, and my batch script did vacuum while
autovacuum did one as well on the other session at the same time.
I found the vacuum analyze conflicts each other sometime...
so I want to control vacuum my self.
http://archives.postgresql.org/pgsql-bugs/2002-12/msg00198.php
http://archives.postgresql.org/pgsql-general/2004-05/msg00015.php
Regards,
Hitoshi Harada
> -----Original Message-----
> From: Peter Eisentraut [mailto:peter_e@gmx.net]
> Sent: Sunday, October 22, 2006 10:08 PM
> To: Hitoshi Harada
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [PATCHES] smartvacuum() instead of autovacuum
>
> Hitoshi Harada wrote:
> > I am trying to implement smartvacuum(), which do vacuum only tables
> > having many dead rows, instead of autovacuum.
>
> How is this different from what autovacuum does?
>
> --
> Peter Eisentraut
> http://developer.postgresql.org/~petere/