Bug 152591 - ERROR: relation "pg_catalog.pg_user" does not exist (Can't use any \d commands)
Summary: ERROR: relation "pg_catalog.pg_user" does not exist (Can't use any \d commands)
Status: CLOSED DUPLICATE of bug 149237
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: postgresql (Show other bugs)
(Show other bugs)
Version: 4.0
Hardware: All Linux
Target Milestone: ---
: ---
Assignee: Tom Lane
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2005-03-30 15:54 UTC by Max Kanat-Alexander
Modified: 2013-07-03 03:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-30 18:15:05 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

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

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

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