Search Postgresql Archives

Re: Unused item pointers - can someone explain?

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

 





On 21/11/2007, Elmer <sebastian.franek@xxxxxxxxx> wrote:
Hello,

I vacuumed one of my database tables. In vacuum output I saw the
following information about unused item pointers:

There were 19310 unused item pointers.

As I understand It means that my table's file consists 19310 free
tuple pointers.

After some minutes I run vacuum again. It was quite unexpected for me
that number of unused item pointers was increased to 19351. I thought
unused item pointers are used in first place when new tuples versions
are created but this example makes me think I am wrong. Can someone
explain this to me?


Yes, however....

found x removable

have just been found and are now unused, so on the next run this number will be added to the unused unless they get used again in the mean time.

The number ie the unused is the number of tuples left in the free space map unused since the last vacuum. If its high it may be worth clustering or running vacuum full but only if you don't think you table will never or unlikely to grow (insert) or change (update) by less than that number of records before you next run vacuum.

Generally only worry if the number is very very high (over 10000).

The best way of understanding the numbers is to run vacuum at regular intervals and compare the output.

Peter.

[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