On Thu, Jul 24, 2014 at 3:02 PM, Tom Lane wrote:
> The fact that the planner can avoid that in the presence of a
> simple constant comparison value doesn't make it a good idea to
> use jsonb_path_ops indexes if you do this type of query a lot,
> because in some usages the planner won't see a const
Peter Geoghegan writes:
> The jsonb documentation says of the jsonb_path_ops GIN opclass:
> """
> A disadvantage of the jsonb_path_ops approach is that it produces no
> index entries for JSON structures not containing any values, such as
> {"a": {}}. If a search for documents containing such a str
The jsonb documentation says of the jsonb_path_ops GIN opclass:
"""
A disadvantage of the jsonb_path_ops approach is that it produces no
index entries for JSON structures not containing any values, such as
{"a": {}}. If a search for documents containing such a structure is
requested, it will requi
