On Mon, Oct 18, 2010 at 3:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)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.
I haven't yet been convinced we need or want to relax the rule about
the directory being empty.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2010-10-18 19:03:22|
|Subject: Re: create tablespace fails silently, or succeeds
|Previous:||From: Tom Lane||Date: 2010-10-18 19:02:15|
|Subject: Re: create tablespace fails silently, or succeeds improperly |