Re: Trouble matching a nested value in JSONB entries

From: "Enrico Thierbach" <eno(at)open-lab(dot)org>
To: "Oleg Bartunov" <obartunov(at)postgrespro(dot)ru>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Trouble matching a nested value in JSONB entries
Date: 2018-07-03 10:16:46
Message-ID: 82F5E247-F0E9-40BF-AA5D-C136AB4D8459@open-lab.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Oleg,

>> 1 | {"group_id": 1}
>> 2 | {“group_id": 1}
>> 3 | {“group_id": 2}
>> 4 | {“group_id": 3}

>>
>> PS: Please note that I am currently at postgres 9.5. An update, if
>> necessary, would be possible though.
>
> Upgrade, please !
>
> I have only master 11beta2 right now:
>
> select * from qq where js @> '{"group_id":1}';
> id | js
> ----+-----------------
> 1 | {"group_id": 1}
> 2 | {"group_id": 1}
> (2 rows)

thanks for your answer. Your code does work fine on 9.5 already; what I
would like to achieve is to get records where the group_id entry is 1 or
2, and a fear that

select * from mytable where (metadata @> '{"group_id":1}') OR
(metadata @> '{"group_id”:2}’)

- while doable - would not make the best use of existing indices.

Any more ideas?
Best,
/eno

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Valery Kuzmin 2018-07-03 10:28:26 One transaction and several processes
Previous Message TAKATSUKA Haruka 2018-07-03 10:01:47 Re: Windows 10 got stuck with PostgreSQL at starting up. Adding delay lets it avoid.