> @@ -106,6 +106,18 @@ CREATE OPERATOR CLASS <replaceable > class="parameter">name</replaceable> [ DEFAUL > </listitem> > </varlistentry> > > + <varlistentry> > + <term><literal>NOT BITWISE</literal></term> > + <listitem> > + <para> > + If present, the operator class equality is not the same as equivalence. > + For example, two numerics can compare equal but have different scales. > + Most opclasses implement bitwise equal comparison, alternative > behaviour > + must be set explicitly. > + </para> > + </listitem> > + </varlistentry>
Am I the only one bothered by the fact that this patch (and all downstream discussion) reduces the term "bitwise equality" to simply "bitwise"? It reads really strange to me, both in the resulting SQL grammar as well as in struct names, code comments etc. "This operator class is bitwise." -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
