Re: postrgesql query planner wrong desicion - Mailing list pgsql-admin

From Tom Lane
Subject Re: postrgesql query planner wrong desicion
Date
Msg-id 1217742.1655475572@sss.pgh.pa.us
Whole thread Raw
In response to postrgesql query planner wrong desicion  (Kenny Bachman <kenny.bachman17@gmail.com>)
Responses Re: postrgesql query planner wrong desicion
List pgsql-admin
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 by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Xmax precedes relation freeze threshold errors
Next
From: Vijaykumar Jain
Date:
Subject: Logical replication on two identical databases but diff versions