Skip site navigation (1) Skip section navigation (2)

Help determining values for max_fsm_pages, max_fsm_relations

From: "CHRIS HOOVER" <CHRIS(dot)HOOVER(at)companiongroup(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Help determining values for max_fsm_pages, max_fsm_relations
Date: 2004-09-28 14:24:00
Message-ID: NYc10c26-4e2947ed@companiongroup.com (view raw or flat)
Thread:
Lists: pgsql-admin
I need some help tuning my free space map.  I have about 275 GB of db's spread
across 3 DB servers.  Unfortunetly, due to design and bandwidth issues, I am
not able to vacuum during business hours, and can only vacuum at night.  I am
trying to get my free space map big enough to hold all of the pages needed so
I can do a normal vacuum most nights and not a full.  Can someone please help
me understand how to see what I should set my max_fsm_pages and
max_fsm_relations to.

I'm running 7.3.4.

Thanks,

Chris

P.S.

Here is a sample output from my largest table:

INFO:  --Relation public.largest_table--
INFO:  Pages 467808: Changed 7982, reaped 16553, Empty 0, New 0; Tup 27257500:
Vac 230875, Keep/VTL 0/0, UnUsed 30151, MinLen 107, MaxLen 347; Re-using:
Free/Avail. Space 55977512/36230564; EndEmpty/Avail. Pages 0/37071.
        CPU 9.22s/2.27u sec elapsed 150.27 sec.
INFO:  Index largest_table_pkey: Pages 140132; Tuples 27257500: Deleted 230875.
        CPU 5.35s/7.81u sec elapsed 134.08 sec.
INFO:  Rel largest_table: Pages: 467808 --> 463676; Tuple(s) moved: 113607.
        CPU 1.54s/6.39u sec elapsed 88.06 sec.
INFO:  Index largest_table_pkey: Pages 140132; Tuples 27257500: Deleted 113607.
        CPU 4.10s/2.01u sec elapsed 86.46 sec.

pgsql-admin by date

Next:From: Tom LaneDate: 2004-09-28 14:45:31
Subject: Re: Vacuum full - disk space eaten by WAL logfiles
Previous:From: George EssigDate: 2004-09-28 13:48:03
Subject: Re: tsearch2 poor performance

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group