| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Igal Sapir <igal(at)lucee(dot)org> |
| Cc: | "Psql_General (E-mail)" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unable to Vacuum Large Defragmented Table |
| Date: | 2019-04-08 01:19:37 |
| Message-ID: | CAKJS1f8t0J4682_2CwKx_3i84WaW-HfSPoL71z0x662Z8HCMjA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 8 Apr 2019 at 10:09, Igal Sapir <igal(at)lucee(dot)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's file system.
>
> When I try to run `VACUUM FULL`, the disk usage goes up until it reaches the full capacity of the partition (about 27GB of 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igal Sapir | 2019-04-08 02:19:43 | Re: Unable to Vacuum Large Defragmented Table |
| Previous Message | Adrian Klaver | 2019-04-08 00:10:05 | Re: Unable to Vacuum Large Defragmented Table |