Skip site navigation (1) Skip section navigation (2)

Re: BUG #4116: Cannot create tablespace: could not set permissions on directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Graham Leggett <minfrin(at)sharp(dot)fm>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4116: Cannot create tablespace: could not set permissions on directory
Date: 2008-06-06 23:52:53
Message-ID: 8080.1212796373@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Graham Leggett wrote:
>> This code makes the incorrect assumption that the platform will allow the
>> postgres user to set the permissions using chmod.

> Is this something we should do anything about?

IMHO, no.  The reason for actually doing the chmod is to verify that we
own the directory.  If it fails, we don't own the directory in any
meaningful sense.  I think the complainant's real problem is that he's
misconfigured his SELinux permissions.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: PGSQL TesterDate: 2008-06-07 11:41:39
Subject: Page header error in 8.x ?
Previous:From: Austin LeeDate: 2008-06-06 23:08:08
Subject: BUG #4226: PG_CTL fails to strip admin rights before running postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group