Re: postrgesql query planner wrong desicion
| От | Kenny Bachman |
|---|---|
| Тема | Re: postrgesql query planner wrong desicion |
| Дата | |
| Msg-id | CAC0w7L+huSuV8EbMe5pbS+1b-Akxpbu_RsszLRigiFFq1OLhXw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: postrgesql query planner wrong desicion (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: postrgesql query planner wrong desicion
|
| Список | pgsql-admin |
Hi Tom,
The gist index is used by other queries with LIKE or ILIKE operators. Should I drop the gist index for text or varchar columns?
Tom Lane <tgl@sss.pgh.pa.us>, 17 Haz 2022 Cum, 17:19 tarihinde şunu yazdı:
Kenny Bachman <kenny.bachman17@gmail.com> writes:
> With GIST Index: (Total exec time : 34s)
> Index Scan using "Pool_Party_Code_gist" on "Pool_Party" (cost=0.28..8.30
> rows=1 width=4) (actual time=0.097..0.097 rows=1 loops=330870)
> Index Cond: (("Code")::text =
> 'TEAM-FIXPOWERUSER'::text)
> Without GIST Index: (Total exec time: 4s)
> Index Scan using "Pool_Party_Code_idx" on "Pool_Party" (cost=0.42..8.44
> rows=1 width=4) (actual time=0.007..0.007 rows=1 loops=330870)
> Index Cond: (("Code")::text =
> 'TEAM-FIXPOWERUSER'::text)
Why do you have a gist index on a column that's apparently plain
text (or varchar)? It seems kinda pointless, and the more so if
it duplicates a btree index.
regards, tom lane
В списке pgsql-admin по дате отправления: