| From: | Michael Loftis <mloftis(at)wgops(dot)com> |
|---|---|
| To: | "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: vacuum full doubled database size |
| Date: | 2020-03-13 13:47:32 |
| Message-ID: | CAHDg04sanUvk-DOsdi3-bctxWH7LBgSs=EDBZyP8zo4wYQemVw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zwettler Markus (OIZ) | 2020-03-13 13:48:49 | AW: vacuum full doubled database size |
| Previous Message | Zwettler Markus (OIZ) | 2020-03-13 13:47:26 | pg_upgrade 9.6 to 12 without 9.6 binaries |