Re: pg_basebackup for streaming base backups
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Magnus Hagander <magnus@hagander.net>, Dimitri Fontaine <dimitri@2ndquadrant.fr>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-01-20T01:53:08Z
Lists: pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> writes: > On Thu, Jan 20, 2011 at 2:21 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Fujii Masao <masao.fujii@gmail.com> writes: >>> What I'm worried about is the case where a tablespace is created >>> under the $PGDATA directory. >> What would be the sense of that? If you're concerned about whether the >> code handles it correctly, maybe the right solution is to add code to >> CREATE TABLESPACE to disallow it. > I'm not sure why that's the right solution. Why do you think that we should > not create the tablespace under the $PGDATA directory? I'm not surprised > that people mounts the filesystem on $PGDATA/mnt and creates the > tablespace on it. No? Usually, having a mount point in a non-root-owned directory is considered a Bad Thing. regards, tom lane