Tom Lane 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,
Alvaro Herrera <[EMAIL PROTECTED]> 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
Graham Leggett wrote:
> This code makes the incorrect assumption that the platform will allow the
> postgres user to set the permissions using chmod.
> What this code should be doing is checking that the permissions on the
> directory are 0700, and failing if they are not, leaving it up to the us
The following bug has been logged online:
Bug reference: 4116
Logged by: Graham Leggett
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.11
Operating system: Redhat Enterprise 5
Description:Cannot create tablespace: could not set permissions on
directory
Detai
