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 CF5893A4A36 for ; Fri, 21 Jan 2005 13:53:39 +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 12801-04 for ; Fri, 21 Jan 2005 13:53:29 +0000 (GMT) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by svr1.postgresql.org (Postfix) with ESMTP id B62543A2C8F for ; Fri, 21 Jan 2005 13:53:31 +0000 (GMT) Received: from jfradkin ([66.15.127.235]) by out003.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050121135331.QRYV1106.out003.verizon.net@jfradkin>; Fri, 21 Jan 2005 07:53:31 -0600 From: "Joel Fradkin" To: "'Tom Lane'" Cc: Subject: Re: still having pg_user error Date: Fri, 21 Jan 2005 08:56:32 -0500 Message-ID: <000001c4ffc1$044e0710$797ba8c0@jfradkin> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In-reply-to: <12319.1106286463@sss.pgh.pa.us> X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [66.15.127.235] at Fri, 21 Jan 2005 07:53:31 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.08 tagged_above=0 required=5 tests=AWL, MSGID_DOLLARS X-Spam-Level: *** X-Archive-Number: 200501/187 X-Sequence-Number: 19975 Tom thank you for the reply. I believe I turned all that off during the install (no firewall). But I can try again. 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. At the very least I guess I can do a backup of the database, wipe = everything /var/lib/pgsql/data and try the initd thing (verify SELinux is off; not = sure how I do that, but I will look at the command you mentioned).=20 I am very happy with my progress thus far (have most of my data coming over), but I am frustrated on my lack of knowledge. I have administered Linux before but its been several years and I don't remember much. I am very impressed with the progress with admin tools and such, I just = wish I had a clear idea of the path to get a development postgres box up on fedora and am more then a little worried about administering the = production (we ordered a 4 processor Dell with Red HAT, I believe I will also need = to install it).=20 Again thank you for that piece of advice, I can always re-install Linux = and verify the SELinux option is off, maybe I messed up again. Joel Fradkin =20 Wazagua, Inc. 2520 Trailmate Dr Sarasota, Florida 34243 Tel. 941-753-7111 ext 305 =20 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. =20 =20 -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us]=20 Sent: Friday, January 21, 2005 12:48 AM To: Joel Fradkin Cc: pgsql-sql@postgresql.org Subject: Re: [SQL] still having pg_user error=20 "Joel Fradkin" writes: > Well I re-installed Fedora 3 and updated my postgres and started the = =3D > 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