| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Thomas Kellerer <shammat(at)gmx(dot)net>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL does not choose my indexes well |
| Date: | 2020-04-23 20:36:15 |
| Message-ID: | CAKFQuwbNs3Avhz0vXU3uabymEoxWsXH9bhCiMWDSkhuPt5-mHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Apr 23, 2020 at 1:33 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I find the apparently
> unnecessary cast in the partial-index predicate to be suspicious ---
> maybe that's blocking matching to the WHERE clause?
>
I noticed that too...I suspect its related to the ANALYZE result:
Index Scan using idx_tabla_entidad on entidad (cost=0.56..51121.41
rows=1405216 width=20) (actual time=0.037..242.609 rows=1409985 loops=1)
Index Cond: ((cod_tabla)::bigint = 4)
Since the index condition ended up cast to bigint the OP probably wrote the
predicate to match.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-04-23 20:45:42 | Re: PostgreSQL does not choose my indexes well |
| Previous Message | Tom Lane | 2020-04-23 20:33:07 | Re: PostgreSQL does not choose my indexes well |