From: | Samed YILDIRIM <samed(at)reddoc(dot)net> |
---|---|
To: | aditya desai <admad123(at)gmail(dot)com> |
Cc: | Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: LIKE CLAUSE on VIEWS |
Date: | 2023-01-22 11:40:58 |
Message-ID: | CAAo1mbnR5x2p8sYSs-EO=+c6JfNYZcKtDNi_+vqnCKWdnZ0YZg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Aditya,
If you share your view's query and the query you run against the view, it
would help all of us to understand better.
pg_trgm would be the life saver option for you, of course if you created it
on the right column, with the right expression, and by using the right
indexing method. It doesn't mean you can't use any index and indexes won't
be used because it is a view, well, if you do it right.
https://www.postgresql.org/docs/current/pgtrgm.html
Best regards.
Samed YILDIRIM
On Sun, 22 Jan 2023 at 13:34, aditya desai <admad123(at)gmail(dot)com> wrote:
> Hi,
> Is there any way to improve performance of LIKE clause on VIEWS.
>
> select * From request_vw where upper(status) like '%CAPTURED%' - 28
> seconds.
>
> select * from request_vw where status='CAPTURED'
>
> Application team is reluctant to change queries from the Application side
> to = instead of LIKE.
>
> Also as this is VIEW TRIGRAM nor normal indexes don't get used.
>
>
> Regards,
> Aditya.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rick Otten | 2023-01-22 15:55:13 | Re: LIKE CLAUSE on VIEWS |
Previous Message | aditya desai | 2023-01-22 11:33:46 | LIKE CLAUSE on VIEWS |