| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Michael G(dot) Martin" <michael(at)vpmonline(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: UnUsed Tuple Space Huge |
| Date: | 2002-06-12 22:32:26 |
| Message-ID: | 13163.1023921146@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Michael G. Martin" <michael(at)vpmonline(dot)com> writes:
> VACUUM verbose symbol_Data;
> NOTICE: --Relation symbol_data--
> NOTICE: Pages 767990: Changed 0, Empty 0; Tup 21595176: Vac 0, Keep 0,
^^^^^^
> UnUsed 16560877.
> Total CPU 61.94s/6.94u sec elapsed 179.25 sec.
That seems to be a couple orders of magnitude above the default size of
the free space map (10000 pages IIRC). How big is your database in
total? You definitely need to increase MAX_FSM_PAGES in
postgresql.conf, but I can't tell how far on the basis of this one
datapoint.
You will probably want to do a VACUUM FULL to clean out some of the free
space and then see where you really stand on number of pages.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael G. Martin | 2002-06-12 22:37:11 | Re: UnUsed Tuple Space Huge |
| Previous Message | edison | 2002-06-12 22:22:21 | database testing |