Re: Query performance issue
| От | Nagaraj Raj |
|---|---|
| Тема | Re: Query performance issue |
| Дата | |
| Msg-id | 2010108831.405412.1599255854719@mail.yahoo.com обсуждение исходный текст |
| Ответ на | Re: Query performance issue (Michael Lewis <mlewis@entrata.com>) |
| Ответы |
Re: Query performance issue
|
| Список | pgsql-performance |
Sorry, I have attached the wrong query planner, which executed in lower environment which has fewer resources:
Updated one,
Thanks,
Rj
On Friday, September 4, 2020, 02:39:57 PM PDT, Michael Lewis <mlewis@entrata.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'
eventtype='LineItemdetailsReceived'
and replenishmenttype = 'DC2SWARRANTY'
В списке pgsql-performance по дате отправления: