Re: Indexing on JSONB field not working - Mailing list pgsql-bugs

From Zhihong Zhang
Subject Re: Indexing on JSONB field not working
Date
Msg-id 83E6A3F7-B1B4-4AD6-905A-BE11D244D35A@gmail.com
Whole thread Raw
In response to Re: Indexing on JSONB field not working  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: Indexing on JSONB field not working  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Indexing on JSONB field not working  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-bugs
The index name is correct and I ran ‘analyze' multiple times since the index is created. I have dozen indexes, some are created when table is created. None of them is in pg_stats.

The pg_stats only contains a row for each column, nothing else. 

The database is on AWS RDS. Does that make any difference?

Zhihong


On Dec 26, 2019, at 11:50 AM, Jeff Janes <jeff.janes@gmail.com> wrote:

On Dec 21, 2019, at 10:17 AM, Jeff Janes <jeff.janes@gmail.com> wrote:

Can you show the output of:

select * from pg_stats where tablename ='float_number_index_path2'

For readability, use the output format which shows the columns down the screen, not across.  In psql, that would toggled on with \x.


On Thu, Dec 26, 2019 at 11:30 AM Zhihong Zhang <zhihong@gmail.com> wrote:
That command yields nothing.

Did you use the actual name of the index (in case its actual name differs from what you showed us in the CREATE INDEX)?  If you did and it doesn't show anything, then I don't think the table has been ANALYZED since the index was created.  Note that ANALYZE and EXPLAIN ANALYZE are different things.  You need to run "ANALYZE assets;" or "VACUUM ANALYZE assets;"

Cheers,

Jeff

pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Indexing on JSONB field not working
Next
From: Kuldip Zalavadiya
Date:
Subject: PostgreSQL Installation Error