Re: Reclaiming space for dropped database

Поиск
Список
Период
Сортировка
От Jerry Sievers
Тема Re: Reclaiming space for dropped database
Дата
Msg-id 87o987upwn.fsf@jsievers.enova.com
обсуждение исходный текст
Ответ на Re: Reclaiming space for dropped database  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
Tom Lane <tgl@sss.pgh.pa.us> writes:

> Alban Hertroys <alban.hertroys@apollovredestein.com> writes:
>
>> Our current development database server is running a bit low on diskspace, 
>> so I dropped an old but rather large database with the intention of 
>> claiming back some space. However, the space remains claimed.
>> This server was upgraded from PG10 to PG11 using pg_upgrade's --link 
>> option.
>
> If you used --link, then all the files would remain hard-linked from both
> the old and new database directories.  You've got to remove them from the
> old DB directory as well.
>
> There's not really any point in keeping around the source DB directory
> once you've completed a --link migration.  Starting the postmaster in
> the old DB directory would be disastrous because the files are
> inconsistent from its standpoint once the new postmaster has modified
> them at all.  (In fact, I think pg_upgrade intentionally makes the old
> directory non-runnable to prevent that error.)  So you might as well

Yeah.  IIRC, it renames control to pg_control.old to avoid accidental
startup.

> just "rm -rf ./10", not only its biggest subdirectory.
>
>             regards, tom lane
>
>

-- 
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net


В списке pgsql-general по дате отправления:

Предыдущее
От: Alan Hodgson
Дата:
Сообщение: Re: Monitoring PITR recovery progress
Следующее
От: Alex Morris
Дата:
Сообщение: how to properly start postgresql with no TCP listeners in ubuntu16.04 LTS