Tom Lane wrote:
> Yeah. We have gotten complaints in the past from people who tried to
> specify a mount point as a tablespace, and it failed because of
> lost+found or the mount dir being root-owned. We've told them to make a
> subdirectory, but that always seemed like a workaround. With the new
> layout there's no longer any strong reason to prevent this case from
> Basically, I'm thinking that given CREATE TABLESPACE LOCATION '/foo/bar'
> the creation and properties of /foo/bar/PG_9.0_201004261 ought to be
> handled *exactly* the way that the -D target directory of initdb is.
> We have more than ten years experience behind the assertion that we're
> dealing with that case in a good way. We should transfer that behavior
> over to tablespace directories rather than inventing something that
> works a shade differently.
> Barring objections, I'll go make it work that way in HEAD and 9.0.
Yes please, thanks.
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ It's impossible for everything to be true. +
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2010-10-18 20:02:14|
|Subject: Re: knngist - 0.8 |
|Previous:||From: Tom Lane||Date: 2010-10-18 19:55:10|
|Subject: Re: Creation of temporary tables on read-only standby servers |