From: "Joel Fradkin" <jfradkin@wazagua.com>
To: "'Tom Lane'" <tgl@sss.pgh.pa.us>
Cc: <pgsql-sql@postgresql.org>
Subject: Re: still having pg_user error 
Date: Fri, 21 Jan 2005 10:51:10 -0500
Message-ID: <000001c4ffd1$08528510$797ba8c0@jfradkin>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <15484.1106317016@sss.pgh.pa.us>

Finally I think that did the trick.
I did see the GUI editor for security and set SELinux to off and re-booted.
I ran the rpm text you gave me
I can use pgadmin with no errors, now for another 12 hours of transferring
data :( so I can work on the views and stored procedures.

This list is a great resource and I appreciate all the ideas comments and
help it has made the difference for me.

Joel Fradkin
 
Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel.  941-753-7111 ext 305
 
jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
 This email message is for the use of the intended recipient(s) and may
contain confidential and privileged information.  Any unauthorized review,
use, disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.
 

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Friday, January 21, 2005 9:17 AM
To: Joel Fradkin
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] still having pg_user error 

"Joel Fradkin" <jfradkin@wazagua.com> writes:
> Is there an action I can take now since it is installed and in theory the
> RPM's are up2date. Sorry I have a few books on postgres Oreily and Sams,
but
> it seems a bit deep on install.

Sure, you can use the RPMs you have.  You want something like (as root)

	service postgresql stop
	rm -rf /var/lib/pgsql/data
	setenforce 0
	service postgresql start

The start script will observe that there's no database directory and
proceed to run initdb for you.


			regards, tom lane