AW: vacuum full doubled database size
| От | Zwettler Markus (OIZ) |
|---|---|
| Тема | AW: vacuum full doubled database size |
| Дата | |
| Msg-id | 148e1731fc5645aca8b4a3af271b6500@zuerich.ch обсуждение исходный текст |
| Ответ на | Re: vacuum full doubled database size (Michael Loftis <mloftis@wgops.com>) |
| Список | pgsql-general |
Thanks. How to get rid of it. New vacuum full?
Von: Michael Loftis <mloftis@wgops.com>
Gesendet: Freitag, 13. März 2020 14:48
An: Zwettler Markus (OIZ) <Markus.Zwettler@zuerich.ch>
Cc: pgsql-general <pgsql-general@postgresql.org>
Betreff: Re: vacuum full doubled database size
A vacuum full rebuilds the tables, so yeah if it didn’t successfully complete I would expect a lot of dead data.
On Fri, Mar 13, 2020 at 07:41 Zwettler Markus (OIZ) <Markus.Zwettler@zuerich.ch> wrote:
We did a "vacuum full" on a database which had been interrupted by a network outage.
We found the database size doubled afterwards.
Autovacuum also found a lot of orphaned tables afterwards.
The ophan temp objects went away after a cluster restart while the db size remained doubled.
Any idea?
Postgres 9.6.17
--
"Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds."
-- Samuel Butler
В списке pgsql-general по дате отправления: