I'm trying to create a new tablespace in a directory that postgres
owns, but PG says it cannot set permissions on this directory.
[EMAIL PROTECTED] ~]# su - postgres
-bash-3.1$ mkdir /opt/home/pgdata/mspace/
-bash-3.1$ psql
Welcome to psql 8.1.4, the PostgreSQL interactive terminal.
Type: \cop
On 10/17/06, Douglas McNaught <[EMAIL PROTECTED]> wrote:
"Andras Simon" <[EMAIL PROTECTED]> writes:
> I'm trying to create a new tablespace in a directory that postgres
> owns, but PG says it cannot set permissions on this directory.
...
> This i
On 10/17/06, Tom Lane <[EMAIL PROTECTED]> wrote:
To use a nondefault tablespace, you'd want to tweak the policy to allow
postgres to write that directory tree too. I'm afraid I know too little
about selinux to explain exactly what to do though ... need to learn
that someday ...
Me too...
A
On 10/17/06, Leonel Nunez <[EMAIL PROTECTED]> wrote:
Correction to my prior mail
do this as root :
chcon system_u:object_r:postgresql_db_t /opt/home/pgdata/mspace
When you need to know what config has any directory for SELinux
do a:
ls -lZ /your/dir
and if you need /your/otherdir t
It seems that PG uses the PGDATA directory even for operations
that affect databases on different tablespaces. For example, when
an index is created on a table that is in tablespace TS, the
index ends up in TS (as it should), but first a temporary
file (with size comparable to the final index) is
On 10/17/06, Martijn van Oosterhout wrote:
On Tue, Oct 17, 2006 at 04:56:09PM +0200, Andras Simon wrote:
> As a more drastic example: I created a DB on a tablespace TS, and
> copied a 25 MB file into one of its tables. I ended up having 60
> MB of extra data in $PGDATA/pg_xlog that d
On 10/17/06, Martijn van Oosterhout wrote:
xlogs are recycled. You can control the growth somewhat by playing with
the xlog settings in the config. It should stabilise at about 16MB
times the wal segments.
This is very good news! Thanks,
Andras
---(end of broadcast)-
