Re: *Regarding brin_index on required column of the table - Mailing list pgsql-general

From Durgamahesh Manne
Subject Re: *Regarding brin_index on required column of the table
Date
Msg-id CAJCZko+TaYwNLuQZMg2EEhw1KEuHNxjGOUSjBk=R6tiumSyFyw@mail.gmail.com
Whole thread Raw
In response to Re: *Regarding brin_index on required column of the table  (Alban Hertroys <haramrae@gmail.com>)
List pgsql-general
Thank you all very much for this information

On Sat, Sep 22, 2018 at 12:38 AM Alban Hertroys <haramrae@gmail.com> wrote:


> On 21 Sep 2018, at 17:49, Durgamahesh Manne <maheshpostgres9@gmail.com> wrote:
>
> <Query>

Considering how hard you try to get rid of duplicates, I'm quite convinced that you're at least short a few join conditions. Getting rid of duplicates early has the added benefit of having to aggregate fewer rows, which should drastically improve the performance of this query.

In addition, your approach of using both distinct and group by raises a red flag that you're fighting symptoms (most likely: duplicate results) without understanding their causes. I can't think of a single situation where both are justified in the same (sub-)query.

Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.

pgsql-general by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Help to understand Actual Rows vs Plan Rows from the queryplanner output
Next
From: Laurenz Albe
Date:
Subject: Mysteriously varying index scan costs