public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Table bloat threshold limit to trigger repack
Date: Sun, 8 Feb 2026 11:26:46 -0500
Message-ID: <CANzqJaCMWyPCcYhp0fd0=jatpcExFNsJ6=Gz8ZxEeUHGE-h+MQ@mail.gmail.com> (raw)
In-Reply-To: <CAJCZkoLc=YXc4H2-aGbp2e-R+WsaLRxiAoj2acLP4=A7z+7xAg@mail.gmail.com>
References: <CAJCZkoJF-97BatLoVf1SUBTAX8BrSeX0dgZS+tBOM2imNnGRFQ@mail.gmail.com>
	<CANzqJaCoH2My0YU9cKDDAtSx5vsTyXcpVH9y7WxZCddNmRPU8w@mail.gmail.com>
	<CAJCZkoK-ipKCuiLuc=S=nrNVCPnbsKAUOs6cS9=1kdftcBQFPw@mail.gmail.com>
	<CANzqJaAO4AbdceTA=4bmSA4sCG6viP28hDeeYjYOUe=jzLVbmg@mail.gmail.com>
	<CAJCZkoLc=YXc4H2-aGbp2e-R+WsaLRxiAoj2acLP4=A7z+7xAg@mail.gmail.com>

On Sun, Feb 8, 2026 at 4:44 AM Durgamahesh Manne <[email protected]>
wrote:

> On Sun, 8 Feb, 2026, 13:15 Ron Johnson, <[email protected]> wrote:
>
>> On Sun, Feb 8, 2026 at 12:43 AM Durgamahesh Manne <
>> [email protected]> wrote:
>>
>>> On Sun, 8 Feb, 2026, 10:59 Ron Johnson, <[email protected]> wrote:
>>>
>>>> On Sat, Feb 7, 2026 at 11:19 PM Durgamahesh Manne <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> How much table bloat is acceptable before it affects performance in
>>>>> PostgreSQL?
>>>>>
>>>>
>>>> How big is the table? (For small tables, it doesn't matter.) How active
>>>> is it?  How frequently are records updated?
>>>>
>>>
>>>
>> Hi
>>>
>>> Table size 100gb
>>> I use pgstattuple_approx to get Table bloat is about 16gb as of now
>>> since after repack is done on 27th of January
>>> Fillfactor already in place
>>> It's very critical application with updates on non partitioned table
>>>
>>
>> What did you set the fillfactor to?
>> Have you minimized the number of indexes?  (That lets HOT work better.)
>> How long does it take to VACUUM the table?
>>
>
>
Hi
>
> Fillfactor 80
> 3 composite and pkey on one column as queries use those
> Vacuum 3min to complete
> Here autovacuum 5min to complete during load even with param tuning
>

1. What is autovacuum_vacuum_scale_factor set to?
2. How often does the autovacuum run? (pg_stat_user_tables will tell you.)
3. Do you update any of those indexed columns?
4. How often do queries/reports need to read large chunks of the table (aka
sequentially scan it)?
5. Is performance currently suffering, or are you proactively worrying?

Note: Regular vacuuming eliminates bloat.

-- 
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

view thread (5+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected]
  Subject: Re: Table bloat threshold limit to trigger repack
  In-Reply-To: <CANzqJaCMWyPCcYhp0fd0=jatpcExFNsJ6=Gz8ZxEeUHGE-h+MQ@mail.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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox