| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why no jsonb_exists_path()? |
| Date: | 2015-06-09 18:40:10 |
| Message-ID: | 15089.1433875210@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> I'm noticing a feature gap for JSONB operators; we have no way to do this:
> jsonb_col ? ARRAY['key1','key2','key3']
> ... that is, there is no way for us to check for key existence in an
> indexable fashion. Given that @> already can check the whole path
> including the value, is there some challenge to stopping just short of
> the value I'm not seeing? Or is this just a "didn't get to it yet" issue?
Hm, well, the jsonb_path_ops opclass couldn't do it, because what it
indexes is hashes that include the value. I suppose jsonb_ops could
look for entries that match all of the keys and then see if the ordering
is correct.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2015-06-09 19:54:59 | Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension |
| Previous Message | Josh Berkus | 2015-06-09 18:16:47 | Why no jsonb_exists_path()? |