Re: BUG #17652: Performance degradation after migrating from v13.4 to v14.4

From: Michael Guissine <mguissine(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Alexander Korotkov <akorotkov(at)postgresql(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17652: Performance degradation after migrating from v13.4 to v14.4
Date: 2022-10-19 22:30:16
Message-ID: CACxDrAm+M22=cMK_Ta1Cje0yR8rN2eSpA+QWULKwDs0gx_UgDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thank you all for such super quick responses. We are considering removing
the pg_trgm index and hope that will help!

On Wed, Oct 19, 2022 at 4:36 PM Andres Freund <andres(at)anarazel(dot)de> wrote:

> Hi,
>
> On 2022-10-19 13:20:37 -0700, Peter Geoghegan wrote:
> > On Wed, Oct 19, 2022 at 1:12 PM Andres Freund <andres(at)anarazel(dot)de>
> wrote:
> > > The reason you're seeing this in 14 is likely the following entry in
> the
> > > release notes:
> > >
> > > > Allow GiST/GIN pg_trgm indexes to do equality lookups (Julien
> Rouhaud)
> > > > This is similar to LIKE except no wildcards are honored.
> > >
> > > CCed author/committer of that change. I suspect this would need proper
> costing
> > > to not be inadvertently be used.
> >
> > I am reminded of this recent thread:
> >
> > https://postgr.es/m/3188617.44csPzL39Z@aivenronan
> >
> > (Perhaps you were thinking of the same thing already, but thought I'd
> > mention it, just in case.)
>
> No, I hadn't seen that one. That indeed looks quite relevant...
>
> Greetings,
>
> Andres Freund
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2022-10-20 03:32:07 Re: Documentation error
Previous Message Andres Freund 2022-10-19 20:35:59 Re: BUG #17652: Performance degradation after migrating from v13.4 to v14.4