From: | Robert Simmons <rsimmons514(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Artem Tomyuk <admin(at)leboutique(dot)com>, Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_attribute getting bloated in size |
Date: | 2018-12-20 09:20:54 |
Message-ID: | CAOGTHR6hZuvrAXW7cdSPyQRxWLSpF8p3uTBpTBHPg_OJOJajvQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Dec 14, 2018, 8:33 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at wrote:
> On Fri, 2018-12-14 at 14:21 +0200, Artem Tomyuk wrote:
> > пт, 14 дек. 2018 г. в 14:14, Ron <ronljohnsonjr(at)gmail(dot)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
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Shreeyansh Dba | 2018-12-20 11:43:41 | Re: Shared data dir for multiple postgresql nodes |
Previous Message | Achilleas Mantzios | 2018-12-20 09:18:16 | Re: [External] Shared data dir for multiple postgresql nodes |