| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | soorjith p <soorjithp(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: vacuumdb command |
| Date: | 2009-10-11 15:59:37 |
| Message-ID: | 4AD200E9.9080306@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
soorjith p wrote:
> I used the vacuumdb command. But in its output I cann't see VACUUM.
>
> The last part of output is
>
> DETAIL: 0 dead row versions cannot be removed yet.
> There were 0 unused item pointers.
> 1 pages contain useful free space.
> 0 pages are entirely empty.
> CPU 0.00s/0.00u sec elapsed 0.00 sec.
> INFO: free space map contains 768 pages in 392 relations
> DETAIL: A total of 6720 page slots are in use (including overhead).
> 6720 page slots are required to track all free space.
> Current limits are: 153600 page slots, 1000 relations, using 965 kB.
>
>
> I think if the process is complete then last part of output is VACUUM.
> Is it means the process is not complete?
No. It is complete.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian Karlak | 2009-10-11 16:44:31 | Re: table partitioning & max_locks_per_transaction |
| Previous Message | soorjith p | 2009-10-11 15:31:33 | vacuumdb command |