Re: Aggregate and many LEFT JOIN - Mailing list pgsql-performance

From Michael Lewis
Subject Re: Aggregate and many LEFT JOIN
Date
Msg-id CAHOFxGpb-MdAMWmmHJs48tV+DAxUi57P2XKoLnsqEaVSDXJcFA@mail.gmail.com
Whole thread Raw
In response to Re: Aggregate and many LEFT JOIN  (kimaidou <kimaidou@gmail.com>)
Responses Re: Aggregate and many LEFT JOIN  (kimaidou <kimaidou@gmail.com>)
List pgsql-performance


On Mon, Feb 25, 2019 at 2:44 AM kimaidou <kimaidou@gmail.com> wrote:
I have better results with this version. Basically, I run a first query only made for aggregation, and then do a JOIN to get other needed data.


Not really "fast", but I gained 30%
 

It still seems that disk sort and everything after that is where the query plan dies. It seems odd that it went to disk if work_mem was already 250MB. Can you allocate more as a test? As an alternative, if this is a frequently needed data, can you aggregate this data and keep a summarized copy updated periodically?

pgsql-performance by date:

Previous
From: Corey Huinker
Date:
Subject: Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks.
Next
From: "support@mekong.be"
Date:
Subject: Re: Query slow for new participants