Bug 593414

Summary:	Documentation recommends an unacceptable global statement_timeout of 30 seconds
Product:	[Other] RHQ Project	Reporter:	Larry O'Leary <loleary>
Component:	Documentation	Assignee:	Deon Ballard <dlackey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Corey Welton <cwelton>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.3.1	CC:	tao
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	2.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-12 16:58:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	593121

Description Larry O'Leary 2010-05-18 18:23:57 UTC

http://www.redhat.com/docs/en-US/JBoss_ON/2.3/html/Installation_Guide/Installation_Guide-Prerequisites-Database.html#Installation_Guide-Database-Postgres_Preparation recommends that statement_timeout be set to 30s.  I do not know where this recommendation comes from but as PostgreSQL recommends that this value be 0, I think we should honour that.

Furthermore, 30s does not seem to be adequate to handle data compression in large environments.  This recommendation should be reviewed and the documentation should be corrected to reflect that this value should be evaluated and increased in situations that require it.

We should also change this from a global recommendation to a user setting recommendation:

ALTER USER rhqadmin SET statement_timeout=300000;

Comment 3 Corey Welton 2010-06-02 13:30:20 UTC

QA Verified... I think this documentation note looks good now.

Comment 4 Corey Welton 2010-08-12 16:58:51 UTC

Mass-closure of verified bugs against JON.