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

Поиск

Список

Период

Сортировка

От	Kent Tong
Тема	Re: using sequential scan instead of index for join with a union
Дата	17 мая 2019 г. 12:36:03
Msg-id	CAKs98dEZko_7SudbMCd-PRgyeAaA3xZwWYhySmn_EpK415_7jA@mail.gmail.com обсуждение исходный текст
Ответ на	Re: using sequential scan instead of index for join with a union (Sergei Kornilov <sk@zsrv.org>)
Список	pgsql-performance

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 по дате отправления:

От: Sergei Kornilov
Дата: 17 мая 2019 г., 12:23:19
Сообщение: Re: using sequential scan instead of index for join with a union

От: Tom Lane
Дата: 17 мая 2019 г., 16:35:35
Сообщение: Re: Analyze results in more expensive query plan