Table space not returned to the OS ?

Поиск
Список
Период
Сортировка
От Florents Tselai
Тема Table space not returned to the OS ?
Дата
Msg-id 35BEB990-A045-413D-8F0F-EA372754960C@gmail.com
обсуждение исходный текст
Ответы Re: Table space not returned to the OS ?  (Magnus Hagander <magnus@hagander.net>)
Re: Table space not returned to the OS ?  (Thomas Boussekey <thomas.boussekey@gmail.com>)
Список pgsql-general
Hi,

A few months back (October) I had upgraded a Postgres instance from v12 —> 14.

The database disk size under /var/lib/postgresql/12 was around 800GB+ back then.
Note, that IIRC I had used hard-linking during the upgrade.

In the database itself, lots of things have changed since.
In fact, that database itself has been dropped at some point and restored from a backup.

As I was running out of disk space, I started investigating and found out that

/var/lib/postgresql/12/main/base/16385  —>  886GB+
/var/lib/postgresql/14 —> 400GB

The last modification date on that directory (../12/) appears to be around a month ago,
When the table with relied 16385 was in fact dropped.

Now, In my update scripts (I use this db as an OLAP) I occasionally run VACUUM.

Is it weird that the 886GB space hasn’t been returned to the OS yet?

What’s the safest way to return it to the OS manually?

Thanks




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

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: Differences in Escaped bytea's when creating a plain pg_dump
Следующее
От: Wolfgang Rißler
Дата:
Сообщение: Re: Differences in Escaped bytea's when creating a plain pg_dump