Postgres Pro
Downloads
Home   >   mailing lists

Re: using sequential scan instead of index for join with a union - Mailing list pgsql-performance

From Kent Tong
Subject Re: using sequential scan instead of index for join with a union
Date
Msg-id CAKs98dEZko_7SudbMCd-PRgyeAaA3xZwWYhySmn_EpK415_7jA@mail.gmail.com
Whole thread Raw
In response to Re: using sequential scan instead of index for join with a union  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-performance
Tree view
Hi, Sergei

Thanks! I've just double checked and they are the same:

\d notice
 id             | bigint                      |           | not null | nextval('notice_id_seq'::regclass)
 mbct_id        | bigint                      |           |          |

\d news
 id             | bigint                      |           | not null | nextval('news_id_seq'::regclass)
 mbct_id        | bigint                      |           |          | 



On Fri, May 17, 2019 at 5:23 PM Sergei Kornilov <sk@zsrv.org> wrote:
Hi

Please check datatypes in union all part. Possible, notice.id or notice.mbct_id datatypes does not match with other tables.

regards, Sergei


--
Kent Tong
IT author and consultant, child education coach

pgsql-performance by date:

Previous
From: Sergei Kornilov
Date:
Subject: Re: using sequential scan instead of index for join with a union
Next
From: Tom Lane
Date:
Subject: Re: Analyze results in more expensive query plan