Re: Frequetly updated partial index leads to bloat on index for Postresql 11

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Dearman <tom(dot)dearman(at)gmail(dot)com>
Cc: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Frequetly updated partial index leads to bloat on index for Postresql 11
Date: 2021-03-18 16:30:30
Message-ID: CAH2-WzmoZBJXYcaBKt2Zjyy-RXiHRsCQyXTcZKiB+n1C4kteTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Mar 18, 2021 at 6:51 AM Tom Dearman <tom(dot)dearman(at)gmail(dot)com> wrote:
> Is this a known issue, are they any ways around it, and if it is an
> issue is there a plan to fix it if a fix is possible?

It's not exactly a known issue per se, but I think the problem here is
related to the fact that you have lots of duplicates, which did
perform rather badly prior to Postgres 12. I bet that you'd benefit
from upgrading to Postgres 12, or especially to Postgres 13. The
B-Tree space management is a lot better now. (Actually, it'll be
better again in Postgres 14.)

--
Peter Geoghegan

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2021-03-18 16:44:29 Re: Open source licenses
Previous Message Laurenz Albe 2021-03-18 16:19:56 Re: postgresql order lowercase before uppercase