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 0B8F3D8D9F for ; Wed, 28 Sep 2005 23:10:46 -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 26673-02 for ; Thu, 29 Sep 2005 02:10:40 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 93A7CD9B70 for ; Wed, 28 Sep 2005 23:10:42 -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 j8T2AjxU006689; Wed, 28 Sep 2005 22:10:45 -0400 (EDT) To: Jeffrey Tenny Cc: pgsql-admin@postgresql.org Subject: Re: Postgresql 8.0.3, symbolic link to /var/lib/pgsql/data/base In-reply-to: <433B3F55.2040407@comcast.net> References: <433AE636.7030506@comcast.net> <8410.1127936570@sss.pgh.pa.us> <433B07F2.40906@comcast.net> <433B086D.7020709@comcast.net> <5092.1127943195@sss.pgh.pa.us> <433B1335.70404@comcast.net> <433B3F55.2040407@comcast.net> Comments: In-reply-to Jeffrey Tenny message dated "Wed, 28 Sep 2005 21:11:49 -0400" Date: Wed, 28 Sep 2005 22:10:45 -0400 Message-ID: <6688.1127959845@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200509/325 X-Sequence-Number: 19062 Jeffrey Tenny writes: > It's clearly selinux though. If I do this: > /usr/sbin/setenforce 0 > Then everything works peachy for my testing. OK, that's pretty conclusive as to the source of the issue. > It's interesting that there are no permission denials > logged in /var/log/messages, but postgresql > says it can't access /var/lib/pgsql/data/base > because permission is denied (in the postgres log). I've run into this more than a few times myself. What I've been told when I complained about it is "that's normal because selinux log messages are rate-limited to avoid inflating the log files too much". Which is plausible in itself, but rate-limiting to zero is not helpful. Feel free to file another gripe in Red Hat's bugzilla. regards, tom lane