Re: create tablespace fails silently, or succeeds improperly

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Dave Cramer <pg@fastcrypt.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-10-18T19:04:14Z
Lists: pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Robert Haas wrote:
> >> Perhaps we should fix the behavior rather than the documentation.
> 
> > We can't fix the behavior because we have to allow an old cluster to
> > keep its tablespace files during a pg_upgrade.  They are given a script
> > to delete those files later, if they want.
> 
> The new *layout* of the files may be forced by pg_upgrade
> considerations, but I don't think that proves much of anything about
> ownership and permissions settings --- especially not the fact that we
> are now enforcing settings that were designed for the data directory
> itself on what is effectively one level up from that.

Agreed.  I was speaking only about the ability to have something in that
top-level directory when you are creating the tablespace.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +