From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: create tablespace fails silently, or succeeds improperly |
Date: | 2010-10-19 02:37:18 |
Message-ID: | 201010190237.o9J2bId18620@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
bruce wrote:
> Tom Lane wrote:
> > Dave Cramer <pg(at)fastcrypt(dot)com> writes:
> > > as seen below create tablespace does not throw an error or appear to
> > > do anything other than register the tablespace.
> >
> > I suspect this behavior is partially intentional, because tablespace
> > creation now involves an extra level of subdirectory. However, it's
> > not clear to me why CREATE TABLESPACE is still changing the permissions
> > on the parent directory. Bruce, exactly what is the rationale here?
>
> Well, the symbolic link from data/pg_tblspc points to the top directory,
> not to the catalog-version-named subdirectory. This was done for
> several reasons, particularly so the directory pointed to by the symlink
> would be exactly the same as that specified by CREATE TABLESPACE, for
> code clarity.
Looking at the pg_upgrade code some more, I found that it was not
removing the PG_VERSION file when deleting <= 8.4 tablespace files.
This might confuse administrators so the attached patch adds the removal
of PG_VERSION. I would like to apply this to master and 9.0.X.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
Attachment | Content-Type | Size |
---|---|---|
/pgpatches/pg_upgrade | text/x-diff | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-10-19 02:56:56 | Re: create tablespace fails silently, or succeeds improperly |
Previous Message | Itagaki Takahiro | 2010-10-19 02:18:34 | Re: PL/JS |