From: | Craig James <cjames(at)emolecules(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: UNION causes horrible plan on JOIN |
Date: | 2019-10-28 23:30:24 |
Message-ID: | CAFwQ8reOEP6xYYCiY2PpoFhOz8+7Tsn0uHSW9Cu3qttK58UJvg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Mon, Oct 28, 2019 at 3:45 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> On Mon, Oct 28, 2019 at 03:40:58PM -0700, Craig James wrote:
> > On Postgres 9.6 (config below), I have a case I don't understand: three
> > tables that can be separately queried in milliseconds, but when put
> > together into one view using UNION, take 150 seconds to query. Here's the
> > rough idea (actual details below):
>
> Do you want UNION ALL ?
>
> UNION without ALL distintifies the output.
> https://www.postgresql.org/docs/current/sql-select.html#SQL-UNION
Interesting idea, thanks. But it makes no difference. Tried it and got the
same bad performance.
Craig
>
>
> Justin
>
--
---------------------------------
Craig A. James
Chief Technology Officer
eMolecules, Inc.
3430 Carmel Mountain Road, Suite 250
San Diego, CA 92121
---------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Craig James | 2019-10-28 23:37:23 | Re: UNION causes horrible plan on JOIN |
Previous Message | Justin Pryzby | 2019-10-28 22:45:53 | Re: UNION causes horrible plan on JOIN |