Kurt Roeckx <Q@ping.be> writes:
> That assumes the memcmp starts from the first char and not from
> the last. If it starts from the last you have undefined
> behaviour.
Hmm. I suppose you could get a reference off the end of memory;
pretty improbable but we have actually seen similar bugs in the field.
Okay, will fix.
regards, tom lane