Re: Table bloat threshold limit to trigger repack - Mailing list pgsql-general

From Ron Johnson
Subject Re: Table bloat threshold limit to trigger repack
Date
Msg-id CANzqJaAO4AbdceTA=4bmSA4sCG6viP28hDeeYjYOUe=jzLVbmg@mail.gmail.com
Whole thread
In response to Re: Table bloat threshold limit to trigger repack  (Durgamahesh Manne <maheshpostgres9@gmail.com>)
Responses Re: Table bloat threshold limit to trigger repack
List pgsql-general
On Sun, Feb 8, 2026 at 12:43 AM Durgamahesh Manne <maheshpostgres9@gmail.com> wrote:
On Sun, 8 Feb, 2026, 10:59 Ron Johnson, <ronljohnsonjr@gmail.com> wrote:
On Sat, Feb 7, 2026 at 11:19 PM Durgamahesh Manne <maheshpostgres9@gmail.com> 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?

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


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?

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

pgsql-general by date:

Previous
From: Durgamahesh Manne
Date:
Subject: Re: Table bloat threshold limit to trigger repack
Next
From: Durgamahesh Manne
Date:
Subject: Re: Table bloat threshold limit to trigger repack