Bug 684049 - Postgres Configuration Needs Clarification
Summary: Postgres Configuration Needs Clarification
Alias: None
Product: RHQ Project
Classification: Other
Component: Documentation
Version: unspecified
Hardware: All
OS: All
medium vote
Target Milestone: ---
: ---
Assignee: Deon Ballard
QA Contact: Mike Foley
Depends On:
Blocks: jon3
TreeView+ depends on / blocked
Reported: 2011-03-10 23:36 UTC by George
Modified: 2012-06-06 15:50 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2012-06-06 15:50:56 UTC

Attachments (Terms of Use)

Description George 2011-03-10 23:36:17 UTC
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

How reproducible:

Steps to Reproduce:
1. Go to the URL above
2. Scroll down slightly to section
3. The example says to set max_fsm_pages = 100000 
Actual results:
The user is led to believe they can set max_fsm_pages in postgresql.conf.

Expected results:
Either remove the mas_fsm_pages property or specify that it only applies to postgres 8.3 and earlier.

Additional info:

"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."

Comment 1 John Mazzitelli 2011-03-25 18:33:56 UTC
making sure this blocks on rhq4 so we remember do change this in the RHQ wiki docs

Comment 2 Ian Springer 2011-04-01 14:04:39 UTC
I've updated the RHQ docs (http://www.rhq-project.org/display/JOPR2/PostgreSQL#PostgreSQL-postgresql.conf)

Comment 4 Robert Buck 2011-11-29 17:07:19 UTC

Note You need to log in before you can comment on or make changes to this bug.