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,
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
Hi,
As far as I can tell from the documentaion, it is impossible to tell the
postmaster daemon to bind to just a single IP address - only to a
specific port on all IP addresses. This makes hardening the box
postgresql is running on impossible.
Is there a workaround to this? (other than trying to
