X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0CF8FD9C8C for ; Thu, 3 Nov 2005 14:12:46 -0400 (AST) 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 15766-08 for ; Thu, 3 Nov 2005 18:12:39 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3D8AEDB4F9 for ; Thu, 3 Nov 2005 14:09:47 -0400 (AST) 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 jA3I9lvD025920; Thu, 3 Nov 2005 13:09:47 -0500 (EST) To: fred.pope@satcomresources.com Cc: pgsql-admin@postgresql.org Subject: Re: Error:PG_DUMP relation pg_user does not exist In-reply-to: <43629636.4050906@satcomresources.com> References: <43629636.4050906@satcomresources.com> Comments: In-reply-to Fred Pope message dated "Fri, 28 Oct 2005 15:20:54 -0600" Date: Thu, 03 Nov 2005 13:09:47 -0500 Message-ID: <25919.1131041387@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.006 required=5 tests=[AWL=0.006] X-Spam-Score: 0.006 X-Spam-Level: X-Archive-Number: 200511/34 X-Sequence-Number: 19407 Fred Pope writes: > I am running Postgresql 7.4.7. on RedHat ES-64 version 4 on a > Dual-Opteron Dual Core system. > I am having problems with the pg_dump command due to improper > initialization of the Database cluster on RH ES 4. Yeah, this is a known problem in some earlier releases of the RHEL4 postgres RPMs --- if you tried to run the initdb with SELinux enforcement enabled, a lot of the init steps fail silently, and you end up with no pg_user view, nor several other important things. > > ERROR: permission denied to create "pg_catalog.pg_user" > DETAIL: System catalog modifications are currently disallowed. > > So my question now is how do I enable system catalog modifications. Stand-alone backend with -O command-line option. As soon as you are able to dump your data, I'd recommend redoing initdb with SELinux off (or update to a newer RPM which works around the problem, then initdb). regards, tom lane