Red Hat Bugzilla – Bug 684049
Postgres Configuration Needs Clarification
Last modified: 2012-06-06 11:50:56 EDT
Description of problem:
The postgresql.conf configuration example shows that you can set the max_fsm_pages property, but this is no longer applicable as of postgres 8.4. In fact, postgres will not start up if you try to set this property.
Version-Release number of selected component (if applicable): 2.4
Steps to Reproduce:
1. Go to the URL above
2. Scroll down slightly to section 126.96.36.199.1
3. The example says to set max_fsm_pages = 100000
The user is led to believe they can set max_fsm_pages in postgresql.conf.
Either remove the mas_fsm_pages property or specify that it only applies to postgres 8.3 and earlier.
"The FSM was rewritten for PostgreSQL 8.4, so earlier advice is no longer applicable. The max_fsm_pages and max_fsm_relations settings are gone, as the new FSM is self-adapting (more info). autovacuum is enabled by default and should remain so, as vacuum much less invasive in 8.4 than before thanks to visibility maps."
making sure this blocks on rhq4 so we remember do change this in the RHQ wiki docs
I've updated the RHQ docs (http://www.rhq-project.org/display/JOPR2/PostgreSQL#PostgreSQL-postgresql.conf)
This is in the 3.0 docs:
I also have it in the 2.4 docs; I just need to update the public build: