X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9476A53696 for ; Sat, 7 May 2005 01:40:05 -0300 (ADT) 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 49570-08 for ; Sat, 7 May 2005 04:40:03 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 0218753695 for ; Sat, 7 May 2005 01:40:01 -0300 (ADT) 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 j474e0Xt029000; Sat, 7 May 2005 00:40:00 -0400 (EDT) To: Daniel Browning Cc: pgsql-admin@postgresql.org Subject: Re: Backup when the database is missing all of the pg_* tables In-reply-to: <20050505181754.GA9167@kavod.com> References: <20050505181754.GA9167@kavod.com> Comments: In-reply-to Daniel Browning message dated "Thu, 05 May 2005 11:17:54 -0700" Date: Sat, 07 May 2005 00:40:00 -0400 Message-ID: <28999.1115440800@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200505/83 X-Sequence-Number: 17512 Daniel Browning writes: > I've been bitten by the "SELinux silently ruins initdb" bug as reported by Tom > Lane: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149237 and another > user: http://www.mail-archive.com/pgsql-bugs@postgresql.org/msg11191.html While I have not tried to get out of that situation myself, I think it should be doable. The basic point is that the SELinux bug^H^H^Hsecurity policy prevented certain parts of the initdb script from taking effect; in particular those that created system views such as pg_user. So what you gotta do is execute those CREATE VIEW commands by hand as superuser, and then pg_dump should work. I think. The parts of initdb that were foiled are the parts that look like postgres <