| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | nikhil raj <nikhilraj474(at)gmail(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Query went slow all of sudden. ON V 11.3 |
| Date: | 2019-10-04 19:07:24 |
| Message-ID: | CAHOFxGofY1e8UEBcvPvjcM05s0Zj+qy4YTZhBMMFrcA40kWPAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
What are approx row counts and distribution of data in the concerned tables
and columns? Have you run EXPLAIN (query plan) to get the plan that will be
executed and can you paste on https://explain.depesz.com/ and share the
link that results?
Do you have an index on LOWER( cr ) on table temp_10032019020721_4470?
Do you have an index on LOWER( c_pagealias ) on table t_ages?
Do you have an index on LOWER( c_id ) on table t_meners?
If temp_10032019020721_4470 is truly temp table, was it analyzed after
creating/inserting/updating/deleting data last, so that the optimizer knows
the number of distinct values, how many rows, most common values, etc?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-10-06 20:30:39 | Re: Query went slow all of sudden. ON V 11.3 |
| Previous Message | nikhil raj | 2019-10-04 13:58:54 | Re: Query went slow all of sudden. ON V 11.3 |