| From: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Table bloat threshold limit to trigger repack |
| Date: | 2026-02-08 05:43:07 |
| Message-ID: | CAJCZkoK-ipKCuiLuc=S=nrNVCPnbsKAUOs6cS9=1kdftcBQFPw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 8 Feb, 2026, 10:59 Ron Johnson, <ronljohnsonjr(at)gmail(dot)com> wrote:
> On Sat, Feb 7, 2026 at 11:19 PM Durgamahesh Manne <
> maheshpostgres9(at)gmail(dot)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
Regards
Durga Mahesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2026-02-08 07:45:37 | Re: Table bloat threshold limit to trigger repack |
| Previous Message | Ron Johnson | 2026-02-08 05:29:14 | Re: Table bloat threshold limit to trigger repack |