<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Apr 9, 2014 at 10:37 AM, Heikki Linnakangas
<spandir="ltr"><<a href="mailto:hlinnakangas@vmware.com" target="_blank">hlinnakangas@vmware.com</a>></span>
wrote:<br/><blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div
class="">Theship has cleatly sailed to add parameterized opclasses to 9.4, but let's keep it in mind when we decide on
thedefaults.<br /></div><br /> In the absence of parameterizable opclasses, it would be much more flexible to have
opclassesthat index, keys, values, key-value pairs and paths separately, instead of the current json_ops and
json_hash_opsopclasses which index all of those in the same index. That way, if you only e.g. ever query on the
existenceof a key, you'd only need to index the keys.<br /><br /> I don't understand how we ended up with the current
dichotomyof json_ops and json_hash_ops...</blockquote><div class="gmail_quote"><br /></div><div class="gmail_quote">+1
forparameterizable opclasses</div><br />------<br /> With best regards,<br />Alexander Korotkov. </div></div></div>
