Re: pg_trgm upgrade to 1.6 led to load average increase

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Nicolas Seinlet <nicolas(at)seinlet(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_trgm upgrade to 1.6 led to load average increase
Date: 2026-01-20 16:34:17
Message-ID: b6443638-9947-474b-ac5a-967e89142387@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/20/26 00:50, Nicolas Seinlet wrote:
> Hello,
>
> we've upgraded the pg_trgm extension from 1.0 to 1.6 on our production
> database, while sticking our postgresql cluster version to 16. This led
> to an increase in the load average of the server (twice the load average
> on our use case). After investigation, we found our issue was linked to :
> https://github.com/postgres/postgres/
> commit/935f6666502250abde8615bc7805a6e5aa05a066 <https://github.com/
> postgres/postgres/commit/935f6666502250abde8615bc7805a6e5aa05a066>
>
> We issue queries like :
> SELECT model, res_id FROM ir_model_data WHERE module='base' AND
> name='public_user';

You need to provide the table definition, including indexes.

> Thanks in advance,
>
> Nicolas
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Matt Magoffin 2026-01-20 18:36:42 Collation with upper and numeric comparing in unexpected way
Previous Message Erik Wienhold 2026-01-20 10:51:35 Re: Request for cryptographic mechanisms used in PostgreSQL