From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Vacuum not working
Date: Thu, 8 Oct 2020 13:25:14 -0500
Message-ID: <5ca002b5-8610-852d-ab75-19ed1be514b1@gmail.com> (raw)
In-Reply-To: <1e53e269f55345a387ed6030285a0f30@izum.si>
References: <1e53e269f55345a387ed6030285a0f30@izum.si>
On 10/8/20 12:32 PM, Domen Šetar wrote:
>
> Hi guys,
>
> I have following problem: I use POWA to collect performance data from 20
> postgresql servers. Vaccum doesn't clean the largest table after POWA
> database is growing large. Here are data taken at 19:27:
>
> relname | last_vacuum | last_autovacuum |
> n_tup | dead_tup | av_threshold | expect_av
>
> --------------------------------------------+-------------+------------------+----------------+----------------+----------------+-----------
>
> powa_all_relations_history_current | | 2020-10-08 18:24 |
> 162,254,592 | 82,045,219 | 162,280 | *
>
> Can you please advise me how to tune poasgresql vacuum parameters to get
> this table cleaned? All other tables are vacummed as expected.
>
Is there an open transaction causing the vacuum to not free thee dead tuples?
--
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: Vacuum not working
In-Reply-To: <5ca002b5-8610-852d-ab75-19ed1be514b1@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