Re: record identical operator

On 2013-09-13 15:13:20 -0700, Kevin Grittner wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>
> > I am not actually that concerned with MVCs using this, you're quite
> > capable of analyzing the dangers. What I am wary of is exposing an
> > operator that's basically broken from the get go to SQL.
> > Now, the obvious issue there is that matviews use SQL to refresh :(
>
> I'm not sure why these operators are more broken or dangerous than
> those which already exist to support the text_pattern_ops and
> bpchar_pattern_ops operator families.  I could overload those
> operator names as much as possible if that seems better.  As I said
> at the start of the thread, I have no particular attachment to
> these operator names.  For example, that would mean using ~>=~ as
> the operator for record_image_ge() instead of using >==.  It would
> be trivial to make that adjustment to the patch.

Hm. I don't see the similarity. Those have pretty clearly defined
behaviour. Not one that's dependendant on padding bytes, null bitmaps
that can or cannot be present and such.

I guess we need input from others here.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services