Re: Unable to Vacuum Large Defragmented Table - Mailing list pgsql-general

From David Rowley
Subject Re: Unable to Vacuum Large Defragmented Table
Date
Msg-id CAKJS1f8t0J4682_2CwKx_3i84WaW-HfSPoL71z0x662Z8HCMjA@mail.gmail.com
Whole thread Raw
In response to Unable to Vacuum Large Defragmented Table  (Igal Sapir <igal@lucee.org>)
Responses Re: Unable to Vacuum Large Defragmented Table  (Igal Sapir <igal@lucee.org>)
List pgsql-general
On Mon, 8 Apr 2019 at 10:09, Igal Sapir <igal@lucee.org> wrote:
>
> I have a table for which pg_relation_size() shows only 31MB, but pg_total_relation_size() shows a whopping 84GB.
>
> The database engine is running inside a Docker container, with the data mounted as a volume from a partition on the
host'sfile system.
 
>
> When I try to run `VACUUM FULL`, the disk usage goes up until it reaches the full capacity of the partition (about
27GBof free space), at which point it fails.
 

That sort of indicates that the table might not be as bloated as you
seem to think it is.  Remember that variable length attributes can be
toasted and stored in the relation's toast table.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Unable to Vacuum Large Defragmented Table
Next
From: Igal Sapir
Date:
Subject: Re: Unable to Vacuum Large Defragmented Table