Joshua D. Drake wrote:
Johannes Konert wrote:
But that is not my point. The question is where I can change the
enforced chmod 700 postgresql always wants me to set.
You can't.
You can however change the postgresql.conf to put look for files
somewhere besides $PGDATA and thus you would be able to back them up.
With postgresql.conf I can change the path to the data-dir, but
postgresql checks the chmod 700 on that directory either. So only the
logfiles can be written and accessed somewhere else. The data itself is
still only accessible by the postgres-user.
Anything else in there you should be grabbing via pg_dump anyway.
So you suggest not to backup the filesystem-files, but to do a dump
instead? Does this work together with PITR as described in 23.3.
(http://www.postgresql.org/docs/8.2/interactive/continuous-archiving.html#BACKUP-BASE-BACKUP).
I want to make a full backup every night of a heavy DB while it is
running. Combined with short-term-WAL-archiving. Getting the WAL-files
is easy by using the config-parameter archive_command, but to copy and
backup the "base backup" once a day is impossible if I cannot access the
data-files.
Will the described backup&restore work as well with a dump + WAL-files?
Then I could forget about copying the file-system-files....
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
