-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Feb 26, 2007 at 06:21:50PM +0900, Galy Lee wrote:
> Hi
> 
> We are developing a new feature for vacuum, here is a brief overview
> about it.

[...]

> Concurrent vacuum mainly has the following steps to vacuum a table:
> 
>   1. scan heap to collect dead tuple list
>   2. (if the table has indexes) scan and sweep indexes
>   3. sweep dead tuples collected in step 1
>   4. perform additional index cleanup operation
>   5. (if a certain of free space found) truncate table
>   6. register free space to FSM
>   7. update statistics of the table

[...]

> This implementation accepts stop request at *blocks level* in step 1-4.

WARNING: I don't really know what I'm talking about -- but considering
that vaccuming a large table across several "maintainance windows" is
one of the envisioned scenarios, it might make sense to try to update
the statistics (i.e. to do partially step 7) on each partial run.
Otherwise the table's stats might wander off for quite long times?

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFF4rpkBcgs9XrR2kYRAoZ1AJwMOSpxlbVSYtPKitEhjem5Jrax7gCeMokx
8DLhqBv9QrtGIDPKOKUi9qw=
=WIiA
-----END PGP SIGNATURE-----


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

Reply via email to