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

From Jeff Janes
Subject Re: Indexing on JSONB field not working
Date
Msg-id CAMkU=1z4do7EF5K4Kz2rjy8R_ELnGEket-TWwa=YwjMwMb_RuA@mail.gmail.com
Whole thread Raw
In response to Re: Indexing on JSONB field not working  (Zhihong Zhang <zhihong@gmail.com>)
Responses Re: Indexing on JSONB field not working  (Zhihong Zhang <zhihong@gmail.com>)
List pgsql-bugs
On Thu, Dec 26, 2019 at 11:58 AM Zhihong Zhang <zhihong@gmail.com> wrote:
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?

I used an RDS 11.5 (not Aurora) instance, and had no trouble getting or seeing the statistics on the expressional index when logged in as the table owner.  They were populated by `ANALYZE assets;`, or by `ANALYZE;`, or by just letting auto-analyze run (if there was enough turn over after the index was created to trigger auto-analyze).

Can you do  `pg_dump -s -t assets ...` to get a full description of the table?  If you don't want to share the full description, make sure whatever simplifications you do to it don't prevent the problem from reproducing.

Cheers,

Jeff

pgsql-bugs by date:

Previous
From: "Zhihong Zhang"
Date:
Subject: RE: Indexing on JSONB field not working
Next
From: Tom Lane
Date:
Subject: Re: Indexing on JSONB field not working