X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id E0FF93A4ACA
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 21 Jan 2005 05:47:48 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 54828-02
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 21 Jan 2005 05:47:45 +0000 (GMT)
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by svr1.postgresql.org (Postfix) with ESMTP id DA9563A4A4E
	for <pgsql-sql@postgresql.org>; Fri, 21 Jan 2005 05:47:45 +0000 (GMT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0L5lhw2012320;
	Fri, 21 Jan 2005 00:47:44 -0500 (EST)
To: "Joel Fradkin" <jfradkin@wazagua.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: still having pg_user error 
In-reply-to: <000001c4ff54$6f427aa0$797ba8c0@jfradkin> 
References: <000001c4ff54$6f427aa0$797ba8c0@jfradkin>
Comments: In-reply-to "Joel Fradkin" <jfradkin@wazagua.com>
	message dated "Thu, 20 Jan 2005 19:59:16 -0500"
Date: Fri, 21 Jan 2005 00:47:43 -0500
Message-ID: <12319.1106286463@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL
X-Spam-Level: 
X-Archive-Number: 200501/183
X-Sequence-Number: 19971

"Joel Fradkin" <jfradkin@wazagua.com> writes:
> Well I re-installed Fedora 3 and updated my postgres and started the =
> service
> (no command line stuff).

> When I connected using pgadmin I still got the sp_user error.

Fedora 3?  You should've mentioned that before.  I'll bet you've got
SELinux enabled in enforcement mode.  SELinux interferes with initdb
and I believe a missing pg_user view is one of the symptoms.

This is fixed in the very latest postgresql and selinux-policy-targeted
RPMs (u need both), but the path of least resistance is often to dial
SELinux down to permissive mode (sudo /usr/sbin/setenforce 0) for long
enough to do the initdb.

If you're running SELinux in strict rather than targeted policy, good
luck ... I honestly haven't tried that one at all ...

			regards, tom lane