Re: pg_attribute getting bloated in size - Mailing list pgsql-admin

From Robert Simmons
Subject Re: pg_attribute getting bloated in size
Date
Msg-id CAOGTHR6hZuvrAXW7cdSPyQRxWLSpF8p3uTBpTBHPg_OJOJajvQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_attribute getting bloated in size  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-admin


On Fri, Dec 14, 2018, 8:33 AM Laurenz Albe <laurenz.albe@cybertec.at wrote:
On Fri, 2018-12-14 at 14:21 +0200, Artem Tomyuk wrote:
> пт, 14 дек. 2018 г. в 14:14, Ron <ronljohnsonjr@gmail.com>:
> > On 12/14/2018 05:29 AM, Laurenz Albe wrote:
> > > Artem Tomyuk wrote:
> > >> Why autovacuum cant delete those rows?
> > > Either long running transactions (check pg_stat_activity)
> > > or prepared transactions (check pg_prepared_xacts)
> > > or stale replication slots (check pg_replication_slots).
> >
> > Would a manual "VACUUM FULL pg_attribute;" solve the problem?
>
> yes, it helps

Only if the problems have been removed.
Otherwise, VACUUM (FULL) won't help.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com


pgsql-admin by date:

Previous
From: Achilleas Mantzios
Date:
Subject: Re: [External] Shared data dir for multiple postgresql nodes
Next
From: Shreeyansh Dba
Date:
Subject: Re: Shared data dir for multiple postgresql nodes