Re: Question on execution plan and suitable index
| От | Laurenz Albe |
|---|---|
| Тема | Re: Question on execution plan and suitable index |
| Дата | |
| Msg-id | cf0bc9aabf8a47705310b7dbf8f341aae4b1849c.camel@cybertec.at обсуждение исходный текст |
| Ответ на | Re: Question on execution plan and suitable index (yudhi s <learnerdatabase99@gmail.com>) |
| Ответы |
Re: Question on execution plan and suitable index
|
| Список | pgsql-general |
On Mon, 2026-02-16 at 16:09 +0530, yudhi s wrote: > I have updated the plan below. While trying to replace actual binds and > the objects with sample names some lines got missed initially it seems. > > https://gist.github.com/databasetech0073/f564ac23ee35d1f0413980fe4d00efa9 Thanks. Does the filter on "due_date" eliminate many rows in "orders"? If yes, and an index on that column would actually perform better (which you could test with enable_seqscan = off), perhaps your "random_page_cost" parameter is set too high. Where you can certainly make a difference is the repeated scan on "event_audit_log". An index on (request_id, event_comment_text, created_at) should speed up that part. Yours, Laurenz Albe
В списке pgsql-general по дате отправления: