AW: vacuum full doubled database size

Thanks. How to get rid of it. New vacuum full?

Von: Michael Loftis <mloftis(at)wgops(dot)com>
Gesendet: Freitag, 13. März 2020 14:48
An: Zwettler Markus (OIZ) <Markus(dot)Zwettler(at)zuerich(dot)ch>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)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(dot)Zwettler(at)zuerich(dot)ch<mailto:Markus(dot)Zwettler(at)zuerich(dot)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