BUG #3120: relation "pg_catalog.pg_user"
The following bug has been logged online:
Bug reference: 3120
Logged by: ravishankar
Email address: ravishankar@celcabs.com
PostgreSQL version: 7.4.6
Operating system: Redhat ES 4.0
Description: relation "pg_catalog.pg_user"
Details:
If I attempt the commands "\d" in psql, I get this:
ERROR: relation "pg_catalog.pg_user" does not exist
Can anyone suggest or help how to comeout of this problem?
"ravishankar" <ravishankar@celcabs.com> writes:
PostgreSQL version: 7.4.6
Operating system: Redhat ES 4.0
If I attempt the commands "\d" in psql, I get this:
ERROR: relation "pg_catalog.pg_user" does not exist
SELinux problem. See, eg,
http://archives.postgresql.org/pgsql-bugs/2007-02/msg00174.php
regards, tom lane
Tom Lane wrote:
"ravishankar" <ravishankar@celcabs.com> writes:
PostgreSQL version: 7.4.6
Operating system: Redhat ES 4.0If I attempt the commands "\d" in psql, I get this:
ERROR: relation "pg_catalog.pg_user" does not existSELinux problem. See, eg,
http://archives.postgresql.org/pgsql-bugs/2007-02/msg00174.php
Can we improve that error message by checking for pg_user and SELinux,
and suggesting that SELinux is the cause?
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Bruce Momjian <bruce@momjian.us> writes:
Tom Lane wrote:
"ravishankar" <ravishankar@celcabs.com> writes:
PostgreSQL version: 7.4.6
^^^^^^^^^^^^^^
Can we improve that error message by checking for pg_user and SELinux,
and suggesting that SELinux is the cause?
We're not in the business of inventing new error message texts for
long-gone releases. Particularly since the OP's problem would be
actually fixed, not just band-aided over, if he were running a newer
release.
regards, tom lane
Tom Lane wrote:
Bruce Momjian <bruce@momjian.us> writes:
Tom Lane wrote:
"ravishankar" <ravishankar@celcabs.com> writes:
PostgreSQL version: 7.4.6
^^^^^^^^^^^^^^
Can we improve that error message by checking for pg_user and SELinux,
and suggesting that SELinux is the cause?We're not in the business of inventing new error message texts for
long-gone releases. Particularly since the OP's problem would be
actually fixed, not just band-aided over, if he were running a newer
release.
Oh, so this would not be a problem in newer PostgreSQL releases. I
thought it was at general SELinux problem.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Bruce Momjian <bruce@momjian.us> writes:
Tom Lane wrote:
We're not in the business of inventing new error message texts for
long-gone releases. Particularly since the OP's problem would be
actually fixed, not just band-aided over, if he were running a newer
release.
Oh, so this would not be a problem in newer PostgreSQL releases. I
thought it was at general SELinux problem.
No, the problem is specifically that Red Hat's first RHEL4 Postgres
releases hadn't been tested adequately under SELinux. (Which is surely
my fault, but too late now.) I see no point in putting a test into
7.4.17 for a problem that was fixed in 7.4.7 or thereabouts.
regards, tom lane