From: hubert depesz lubaczewski <depesz@depesz.com>
To: Artem Tomyuk <admin@leboutique.com>
Cc: Keith <keith@keithf4.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: how to shrink pg_attribute table in some database
Date: Mon, 26 Mar 2018 16:17:56 +0200
Message-ID: <20180326141756.GB708@depesz.com> (raw)
In-Reply-To: <CANYYVqLSEdHVzXiUUHp+mPM+X5tbbP_oOfHh5-RJGoTkReGsmA@mail.gmail.com>
References: <CANYYVqKwgR8TK6ar54vbXLc01KH-_ppM=qh6GLQ6edmmexX-EQ@mail.gmail.com>
<CAHw75vuFvy_Tn9ZT0zANugeJOLhrfcmxv4r+XeJV0NszVNmn5Q@mail.gmail.com>
<CANYYVqLSEdHVzXiUUHp+mPM+X5tbbP_oOfHh5-RJGoTkReGsmA@mail.gmail.com>
On Mon, Mar 26, 2018 at 05:15:14PM +0300, Artem Tomyuk wrote:
> For now pg_attribute bloated to 300GB in size, and we have only 260GB's of
> free space on disk.
> In normal situation pg_attribute takes 50mb in size for our DB...
> Can we assume that if we will run vacuum full on pg_attribute it will take
> additional 50MB on disk?
You can estimate by doing:
create table z as select * from pg_Attribute;
and then checking size of z.
bloat there suggests that you have huge churn in tables - like: create
table, drop table, lots of times.
Best regards,
depesz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: depesz@depesz.com, admin@leboutique.com, keith@keithf4.com
Subject: Re: how to shrink pg_attribute table in some database
In-Reply-To: <20180326141756.GB708@depesz.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox