| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Vacuum summary? |
| Date: | 2005-07-11 19:10:41 |
| Message-ID: | 42D2C431.2020606@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
What do you guys think of having a vacuum summary command? E.g.;
VACUUM [FULL] [ANALYZE] SUMMARY
where summary would only print the last lines of a vacuum verbose?
foo=> VACUUM SUMMARY;
INFO: free space map contains 17 pages in 12 relations
DETAIL: A total of 192 page slots are in use (including overhead).
192 page slots are required to track all free space.
Current limits are: 20000 page slots, 1000 relations, using 182 KB.
VACUUM
foo=>
Sincerely,
Joshua D. Drake
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-07-11 19:20:09 | Re: Possible better pg_ctl start/stop handling? |
| Previous Message | Joshua D. Drake | 2005-07-11 19:06:08 | Re: Possible better pg_ctl start/stop handling? |