| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | sugnathi hai <suganhai(at)yahoo(dot)com> |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Performance tunning |
| Date: | 2020-05-30 14:55:36 |
| Message-ID: | CAMkU=1xJTxf6Mj9Gc04ceTCrG2rjf9iMbjB4NOUtqC9OzZnsVg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sat, May 30, 2020 at 3:37 AM sugnathi hai <suganhai(at)yahoo(dot)com> wrote:
> Hi ,
>
> Can you help to tune the below plan
>
It looks like your query (which you should show us) has something like
ORDER BY modifieddate LIMIT 100
It thinks it can walk the index in order, then stop once it collects 100
qualifying rows. But since almost all rows are removed by the join
conditions, it ends up walking a large chunk of the index before finding
100 of them which qualify.
You could try forcing it out of this plan by doing:
ORDER BY modifieddate + interval '0 second' LIMIT 100
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sugnathi hai | 2020-06-01 12:09:33 | Configuration |
| Previous Message | Justin Pryzby | 2020-05-30 14:19:51 | Re: Performance tunning |