Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 152591

Summary:	ERROR: relation "pg_catalog.pg_user" does not exist (Can't use any \d commands)
Product:	Red Hat Enterprise Linux 4	Reporter:	Max Kanat-Alexander <mkanat>
Component:	postgresql	Assignee:	Tom Lane <tgl>
Status:	CLOSED DUPLICATE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	dwalsh, hhorak
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-30 18:15:05 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 Max Kanat-Alexander 2005-03-30 15:54:34 UTC

I'm running RHEL4, and I just downloaded postgresql-server-7.4.7-2.RHEL4.1
today. I started it, it init'ed the DB, and everything seemed fine.

I did an "su - postgres", created a database with createdb, and connected to it
using "psql <db_name>".

When I try to use any \d command that would tell me anything about a table, I
get the error:

ERROR:  relation "pg_catalog.pg_user" does not exist

Comment 1 Max Kanat-Alexander 2005-03-30 17:04:29 UTC

OK, I've managed to repair the issue locally, here's the steps I took that I
*think* fixed it (I did a few other things, too, but I think they were mostly a
no-op):

service postgresql stop
rm -rf /var/lib/pgsql/data
mkdir /var/lib/pgsql/data
chmod go-rwx /var/lib/pgsql/data
restorecon /var/lib/pgsql/data
setenforce 0
su - postgres
initdb
exit
service postgresql start
service postgresql stop
setenforce 1
service postgresql start

I'm not sure that the last little bit of doing the first start before turning
back on SELinux is necessary.

Comment 2 Tom Lane 2005-03-30 18:15:05 UTC

Yeah, this sounds exactly like bug #149237.  I believe this is fixed (or more
accurately, worked around) as of postgresql-7.4.7-3.RHEL4.1.

See also bug #143208

*** This bug has been marked as a duplicate of 149237 ***

Comment 3 Terry Polzin 2005-05-17 20:30:05 UTC

OK so where is postgresql-7.4.7-3.RHEL4.1?  It's not in the errata