Peter Eisentraut <peter_e@gmx.net> writes:
> The return value of memcmp() is also used by bytea and oidvector. As long
> as you don't need comparison results, and memcmp gives wrong results
> consistently then you might even get away with it, but a disfunctional
> oidvector cannot be taken as lightly as the bit types.
oidvector only checks the result for equal or not equal to 0. AFAIK,
the issue with SunOS memcmp is not that it gets equality wrong, it's
that it sorts unequal values wrong. So oidvector will work.
A quick search shows that bit, bytea, and the contrib/tsearch module
are the only places in 7.2 that care about the sign of memcmp's result.
regards, tom lane
