| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kenny Bachman <kenny(dot)bachman17(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: postrgesql query planner wrong desicion |
| Date: | 2022-06-17 14:19:32 |
| Message-ID: | 1217742.1655475572@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Kenny Bachman <kenny(dot)bachman17(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vijaykumar Jain | 2022-06-17 18:34:47 | Logical replication on two identical databases but diff versions |
| Previous Message | Álvaro Herrera | 2022-06-17 09:53:05 | Re: Xmax precedes relation freeze threshold errors |