> Tatsuo Ishii writes:
>
> > The reason why non-8bit clean memcmp has not been a problem with
> > SunOS4 port was just memcmp's return value was evaluated 0 or not.
> > However, bit data type implementation uses the fact that whether the
> > value is greater than or less than 0 and bit type appeared since 7.1.
> > I guess that is the reason why we don't see any memcmp problem before
> > 7.1.
>
> 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.
>
> I've put the SunOS 4 platform under "Unsupported" with the comment
> "memcmp() does not work correctly, so probably not reliable". Seasoned
> SunOS 4 users might know what that implies.
I am working with Tatsuo to test the new memcmp.c on SunOS and will
report back when the test is completed and all regression tests pass.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
