Subject: Re: JOIN on partitions is very slow
To: pgsql-performance@lists.postgresql.org
References: 
 <CAFg0VMDrPS+CQF7z0e2SFNtW3wjWV_jVY2mkEWpF-eeg6jha=w@mail.gmail.com>
 <CAHOFxGodwHOJcn8ioEFfvh_kxZqXCJDP24PxXEkn3uhqFgQBKQ@mail.gmail.com>
 <CAFg0VMAkUn7AJuNo28sm2zXcsJUXKm+ACD2CmZZxZ801PZSiPw@mail.gmail.com>
 <CAHOFxGrjS+bFcD+Fbn7EqnJJ2oMPfQX_FEuDSkMjWxMYkBNemA@mail.gmail.com>
From: Thomas Kellerer <shammat@gmx.net>
Message-ID: <7cdfd0d6-e4d3-7351-f13c-696460853657@gmx.net>
Date: Mon, 23 Mar 2020 17:33:34 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.21)
 Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.5.666
MIME-Version: 1.0
In-Reply-To: 
 <CAHOFxGrjS+bFcD+Fbn7EqnJJ2oMPfQX_FEuDSkMjWxMYkBNemA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Michael Lewis schrieb am 23.03.2020 um 17:16:
> Yes. I can tweak the query. Version of postgres is 9.5.15. I have
> about 20 partitions for company_sale_account table. I do have an
> index on company name.
>
> I need to use DISTINCT as i need to remove the duplicates.
>
>
> DISTINCT is a sign of improper joins most of the time in my
> experience. Often, just changing to group by is faster

As none of the columns of the joined table are used, most probably
this should be re-written as an EXISTS condition.
Then neither GROUP BY nor DISTINCT is needed.