Bug 68363

Summary:	Unable to change PGDATA in postgres
Product:	[Retired] Red Hat Linux	Reporter:	Jeremy Sanders <jss>
Component:	postgresql	Assignee:	Trond Eivind Glomsrxd <teg>
Status:	CLOSED WONTFIX	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-07-09 15:56:25 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:

Description Jeremy Sanders 2002-07-09 15:56:21 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a) Gecko/20020610

Description of problem:
The way postgresql is currently packaged it is hard to change the location of
the database (i.e. PGDATA) without modifying the startup script (which will get
overwritten on updating).

A better way of setting PGDATA (rather than fixing it to /var/lib/pgsql) would
be to see what the home directory of the postgres user is set to and use that.

Comment 1 Trond Eivind Glomsrxd 2002-07-09 19:55:36 UTC

If you have a nice, clean patch which doesn't lead to problems for initscripts,
file ownership etc, you can attact it.

Other than that, I don't see a need and the current way works well - and handles
issues like recognizing older versions of the database and issueing approriate
warnings.