Re: using sequential scan instead of index for join with a union
Kent Tong <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.performance |
|---|---|
| Message-ID | <CAKs98dEZko_7SudbMCd-PRgyeAaA3xZwWYhySmn_EpK415_7jA@mail.gmail.com> |
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 <[email protected]> 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