Search Postgresql Archives

Re: Need help understanding vacuum verbose output

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> That last message prints tups_vacuumed, but those other ones are counting
> all the removed item pointers.  So apparently Gordon had a whole lot of
> pre-existing DEAD item pointers.  I wonder why ...

Perhaps this will help.  Here's the entire test.

Start with a newly loaded table with 5,063,463 rows. 
1. delete 467 rows
2. delete 4,220 rows
3. vacuum
4. delete 5,091 rows
5. delete 3,832 rows
6. delete 10,168 rows
7. delete 10,469 rows
8. delete 16,318 rows
9. vacuum (output shown in original post)

> 13 There were 4687 unused item pointers. 

This corresponds to the 1st 2 steps, I presume, where the 4687 unused
pointer were created by the 1st vacuum.




-- 
View this message in context: http://postgresql.1045698.n5.nabble.com/Need-help-understanding-vacuum-verbose-output-tp2265895p2266912.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux