Re: Indexing on JSONB field not working

> On Dec 27, 2019, at 12:45 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>
> 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.
>

I created a new table ‘assets_copy’ with only 3 columns. I can still reproduce the problem. The pg_dump output is attached.

Thanks!

Zhihong

--
-- PostgreSQL database dump
--
-- Dumped from database version 11.4
-- Dumped by pg_dump version 11.6
SET statement_timeout = 0;
SET lock_timeout = 0;
SET idle_in_transaction_session_timeout = 0;
SET client_encoding = 'UTF8';
SET standard_conforming_strings = on;
SELECT pg_catalog.set_config('search_path', '', false);
SET check_function_bodies = false;
SET xmloption = content;
SET client_min_messages = warning;
SET row_security = off;
SET default_tablespace = '';
SET default_with_oids = false;
--
-- Name: assets_copy; Type: TABLE; Schema: public; Owner: postgres
--
CREATE TABLE public.assets_copy (
id character(20),
_doc jsonb,
floatvalue double precision
);
ALTER TABLE public.assets_copy OWNER TO postgres;
--
-- Name: column_float_value_idx; Type: INDEX; Schema: public; Owner: postgres
--
CREATE INDEX column_float_value_idx ON public.assets_copy USING btree (floatvalue);
--
-- Name: jsonb_float_value_idx; Type: INDEX; Schema: public; Owner: postgres
--
CREATE INDEX jsonb_float_value_idx ON public.assets_copy USING btree ((((_doc #> '{floatValue}'::text[]))::double precision));
--
-- PostgreSQL database dump complete
--