From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: pg_attribute getting bloated in size
Date: Fri, 14 Dec 2018 06:13:49 -0600
Message-ID: <be86101e-fe5e-0edf-620a-78c16fbb0d17@gmail.com> (raw)
In-Reply-To: <2b31f655c7696125284523fa06695429f24d79f8.camel@cybertec.at>
References: <CANYYVq+PXrNTO-W90UChbJ+FL_h0qoEpJ2zXTVGZj_89P9CyTw@mail.gmail.com>
<2b31f655c7696125284523fa06695429f24d79f8.camel@cybertec.at>
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?
--
Angular momentum makes the world go 'round.
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: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: pg_attribute getting bloated in size
In-Reply-To: <be86101e-fe5e-0edf-620a-78c16fbb0d17@gmail.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