| From: | Marc Cousin <cousinmarc(at)free(dot)fr> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: Setting max_fsm_pages | 
| Date: | 2005-11-08 20:08:03 | 
| Message-ID: | 200511082108.03950.cousinmarc@free.fr | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
As we're talking about fsm, I've got a question I've been asking myself for 
some time :
If a cluster is restarted, is the fsm forgotten ? (so does it mean one should 
run a vacuum as soon as the database is restarted ?)
Le Dimanche 06 Novembre 2005 03:44, Carlos Oliva a écrit :
> Should I set the max_fsm_pages to the value reported (vacuum verbose) as
> pages stored or the value reported as total pages needed?  I ran full +
> analyze vacuums in my database (vacuumdb -f -z -v <database name>) a couple
> of times and I got the following reports:
>
> INFO:  free space map: 454 relations, 22274 pages stored; 147328 total
> pages needed
>
> DETAIL:  Allocated FSM size: 1000 relations + 20000 pages = 178 kB shared
> memory
>
>
>
> And
>
>
>
> INFO:  free space map: 454 relations, 22242 pages stored; 147328 total
> pages needed
>
> DETAIL:  Allocated FSM size: 1000 relations + 20000 pages = 178 kB shared
> memory
>
>
>
> I am not sure if I need to raise the max_fsm_pages to something larger than
> 22242 (e.g. 40000) or larger than 147,328.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Mayrhofer | 2005-11-08 20:10:07 | Re: upgrading from backend version 811 to 812 | 
| Previous Message | Jim C. Nasby | 2005-11-08 19:59:57 | Re: upgrading from backend version 811 to 812 |