Re: Wanted: jsonb on-disk representation documentation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Wanted: jsonb on-disk representation documentation
Date: 2014-05-07 19:08:36
Message-ID: 2443.1399489716@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

btw ... in jsonb.h there is this comment:

* Jsonb Keys and string array elements are treated equivalently when
* serialized to text index storage. One day we may wish to create an opclass
* that only indexes values, but for now keys and values are stored in GIN
* indexes in a way that doesn't really consider their relationship to each
* other.

Is this an obsolete speculation about writing jsonb_hash_ops, or is there
still something worth preserving there? If so, what?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-05-07 19:18:55 Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
Previous Message Josh Berkus 2014-05-07 19:06:24 Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers