From: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
---|---|
To: | Alban Hertroys <haramrae(at)gmail(dot)com> |
Cc: | andreas(at)a-kretschmer(dot)de, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: *Regarding brin_index on required column of the table |
Date: | 2018-09-24 07:09:09 |
Message-ID: | CAJCZko+TaYwNLuQZMg2EEhw1KEuHNxjGOUSjBk=R6tiumSyFyw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you all very much for this information
On Sat, Sep 22, 2018 at 12:38 AM Alban Hertroys <haramrae(at)gmail(dot)com> wrote:
>
>
> > On 21 Sep 2018, at 17:49, Durgamahesh Manne <maheshpostgres9(at)gmail(dot)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.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2018-09-24 08:50:15 | Mysteriously varying index scan costs |
Previous Message | Tomas Vondra | 2018-09-23 22:41:32 | Re: Help to understand Actual Rows vs Plan Rows from the query planner output |