Hello all, I think that this patch is useful to decide when to vacuum. It notifies when freespace empties as follows:
$ ./pgbench -i $ ./pgbench -n -t 1000 LOG: FreeSpace for "public.accounts" becomes empty. (stored=1, avg=159, min=128) LOG: FreeSpace for "public.tellers" becomes empty. (stored=1, avg=238, min=40) LOG: FreeSpace for "public.branches" becomes empty. (stored=1, avg=238, min=36) $ vacuumdb VACUUM $ ./pgbench -n -t 2000 LOG: FreeSpace for "public.history" becomes empty. (stored=1, avg=208, min=52) LOG: FreeSpace for "public.accounts" becomes empty. (stored=758, avg=159, min=128) LOG: FreeSpace for "public.branches" becomes empty. (stored=5, avg=191, min=36) LOG: FreeSpace for "public.tellers" becomes empty. (stored=6, avg=184, min=40) Furthermore, this patch detaches empty fsmpages then. Freespaces keep being scanned after they empties, but it seems to be bootless effort. Is this useful? --- ITAGAKI Takahiro <[EMAIL PROTECTED]> NTT Cyber Space Laboratories Nippon Telegraph and Telephone Corporation.
freespace.diff
Description: Binary data
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
