Notification when freespaces empty - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Notification when freespaces empty
Date
Msg-id 20050520144008.3C92.ITAGAKI.TAKAHIRO@lab.ntt.co.jp
Whole thread Raw
Responses Re: Notification when freespaces empty  (Simon Riggs <simon@2ndquadrant.com>)
Re: Notification when freespaces empty  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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 <itagaki.takahiro@lab.ntt.co.jp>
NTT Cyber Space Laboratories
Nippon Telegraph and Telephone Corporation.

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Inherited constraints and search paths (was Re: [GENERAL] Preserving data after updates)
Next
From: Simon Riggs
Date:
Subject: Re: Inherited constraints and search paths (was Re: