From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Table : Bloat grow high
Date: Fri, 11 Nov 2022 12:46:24 -0600
Message-ID: <da8a3249-62e2-233f-7e45-090d3fc026bc@gmail.com> (raw)
In-Reply-To: <BLAPR19MB4626534A9D173ECE0F0A9521A1009@BLAPR19MB4626.namprd19.prod.outlook.com>
References: <BLAPR19MB4626534A9D173ECE0F0A9521A1009@BLAPR19MB4626.namprd19.prod.outlook.com>
On 11/11/22 11:09, Alexis Zapata wrote:
>
> Hi all,
> In postgresql 13.5
Upgrade to at least 13.8. (13.9 was released yesterday.)
> I have a table (size 3.1 GB) and in this table occurs near to 200 updates
> per second, after 2 days the size table is 7 GB and bloat grow to 45% and
> the query operations are degraded. vacuum runs every 5 seconds over this.
> but the bloat growth continues, to solve the
> problem quickly, we have made a replica of the table with a trigger, then
> a copy of the data and in a
> transaction we rename the table, but it would not be the best solution.
> Some suggestion about stop this size increase or parameter to setting up?
Manually vacuum it on a regular basis.
Think about partitioning it on PK boundaries; that way you can vacuum each
child at the same time.
--
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: Table : Bloat grow high
In-Reply-To: <da8a3249-62e2-233f-7e45-090d3fc026bc@gmail.com>
References: <BLAPR19MB4626534A9D173ECE0F0A9521A1009@BLAPR19MB4626.namprd19.prod.outlook.com> <da8a3249-62e2-233f-7e45-090d3fc026bc@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