Re: using sequential scan instead of index for join with a union

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: using sequential scan instead of index for join with a union
From: Sergei Kornilov <sk@xxxxxxxx>
Date: Fri, 17 May 2019 12:23:19 +0300
In-reply-to: <CAKs98dGxcPAyiN7Euw8wjiadVkNj92L+_txgpdVdEfRBDefk-A@mail.gmail.com>
References: <CAKs98dGxcPAyiN7Euw8wjiadVkNj92L+_txgpdVdEfRBDefk-A@mail.gmail.com>

Hi

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

regards, Sergei

Follow-Ups:
- Re: using sequential scan instead of index for join with a union
  - From: Kent Tong

References:
- using sequential scan instead of index for join with a union
  - From: Kent Tong

Prev by Date: using sequential scan instead of index for join with a union
Next by Date: Analyze results in more expensive query plan
Previous by thread: using sequential scan instead of index for join with a union
Next by thread: Re: using sequential scan instead of index for join with a union
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux