From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: create tablespace fails silently, or succeeds improperly |
Date: | 2010-10-19 14:08:48 |
Message-ID: | 9633.1287497328@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> 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.
>>
>> ... why is that a good idea?
> The script already deletes the 8.4 database directories, but leaves
> PG_VERSION behind. Why keep it when all the 8.4 data is gone? The
> script also dates PGDATA for 8.4, so there is nothing left pointing to
> that directory.
Oh, I misunderstood: I thought you were proposing to do this as an
automatic action inside pg_upgrade. If it's part of the cleanup script,
it's fine.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2010-10-19 14:17:06 | Re: knngist - 0.8 |
Previous Message | Alvaro Herrera | 2010-10-19 14:05:55 | Re: WIP: extensible enums |