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 9E12B8B9B27 for ; Wed, 16 Feb 2005 15:37:22 +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 67466-06 for ; Wed, 16 Feb 2005 15:37:15 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 3EEF98BA293 for ; Wed, 16 Feb 2005 15:37:14 +0000 (GMT) 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 j1GFbFMH024233; Wed, 16 Feb 2005 10:37:15 -0500 (EST) To: "Joel Fradkin" Cc: pgsql-admin@postgresql.org Subject: Re: WHat foldsers in the data folder would I need to link to have my data on a different drive? In-reply-to: <000701c51437$bf1a8430$797ba8c0@jfradkin> References: <000701c51437$bf1a8430$797ba8c0@jfradkin> Comments: In-reply-to "Joel Fradkin" message dated "Wed, 16 Feb 2005 09:56:49 -0500" Date: Wed, 16 Feb 2005 10:37:14 -0500 Message-ID: <24232.1108568234@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/141 X-Sequence-Number: 16309 "Joel Fradkin" writes: > I originally used the data_dir conf option to have my data on /pgslq/data, > but am thinking I should do it the way I did the /wal with a link. My > thinking is then the pid would still be in /var not /pgsql, and the stratup > and shutdown would work better. I am just guessing here, not having done the experiment --- but I'm not at all sure that that will let you escape the SELinux policy restrictions. I suspect you will find that you have no choice but to alter the policy to allow the postgres daemon to access your nondefault data area. (Or turn off SELinux, but that might be an overreaction.) It might be possible to make an end-run by using a nondefault installation of Postgres --- if the postmaster executable doesn't live in /usr/bin, I *think* (but am not certain) that the SELinux targeted policy will not think it's supposed to constrain the daemon's actions. Then you are back to relying solely on filesystem permissions; but that seems like plenty to me. regards, tom lane