| From: | Nagaraj Raj <nagaraj(dot)sf(at)yahoo(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com>, Thomas Kellerer <shammat(at)gmx(dot)net> |
| Cc: | Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Query performance issue |
| Date: | 2020-09-04 21:44:14 |
| Message-ID: | 2010108831.405412.1599255854719@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Sorry, I have attached the wrong query planner, which executed in lower environment which has fewer resources:
Updated one,eVFiF | explain.depesz.com
|
|
| |
eVFiF | explain.depesz.com
|
|
|
Thanks,Rj On Friday, September 4, 2020, 02:39:57 PM PDT, Michael Lewis <mlewis(at)entrata(dot)com> wrote:
CREATE INDEX receiving_item_delivered_received ONÂ receiving_item_delivered_received USING btree ( eventtype, replenishmenttype, serial_no, eventtime DESC );
More work_mem as Tomas suggests, but also, the above index should find the candidate rows by the first two keys, and then be able to skip the sort by reading just that portion of the index that matches
eventtype='LineItemdetailsReceived'and replenishmenttype = 'DC2SWARRANTY'
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2020-09-04 21:55:10 | Re: Query performance issue |
| Previous Message | Michael Lewis | 2020-09-04 21:41:23 | Re: Query performance issue |