| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Artem Tomyuk <admin(at)leboutique(dot)com>, Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_attribute getting bloated in size |
| Date: | 2018-12-14 14:33:32 |
| Message-ID: | c742bb3b991357b9aba06b3985630e0e9372fed2.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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 | wambacher | 2018-12-14 15:39:30 | finding queries doing sequential search |
| Previous Message | Artem Tomyuk | 2018-12-14 12:21:50 | Re: pg_attribute getting bloated in size |