From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | wespvp(at)syntegra(dot)com |
Cc: | Postgres List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: max_fsm_pages |
Date: | 2004-07-01 20:19:21 |
Message-ID: | 40E471C9.6010503@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
If you increase max_fsm_pages to a large enough number then the next
vacuum analyze will make all the pages with free space available to be
reused. A normal VACUUM does not actually reclaim space (unless it's at
the end of the table I think), it only marks the space as reuseable.
VACUUM FULL will reclaim space immediately.
Matthew
wespvp(at)syntegra(dot)com wrote:
> If max_fsm_pages is too small and I have space not reclaimed by vacuum, if I
> increase max_fsm_pages and restart postmaster, will the next VACUUM ANALYZE
> relcaim all overlooked pages or must I do a VACUUM FULL?
>
> Wes
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
From | Date | Subject | |
---|---|---|---|
Next Message | Doug McNaught | 2004-07-01 20:28:51 | Re: Error loading trigger in C |
Previous Message | Juan Jose Costello Levien | 2004-07-01 20:02:39 | Re: Error loading trigger in C |