Re: strncmp->memcmp when we know the shorter length

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Gurjeet Singh <singh.gurjeet@gmail.com>, Noah Misch <noah@leadboat.com>, pgsql-hackers@postgresql.org
Date: 2010-12-22T03:24:47Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> If it's done properly, I don't see how this would be a risk.

I'm fairly uncomfortable about the broad swath and low return of this
patch.  Noah is assuming that none of these places are relying on
strncmp to stop short upon finding a null, and I don't believe that
that's a safe assumption in every single place.  Nor do I believe that
it's worth the effort of trying to prove it safe in most of those
places.

I think this might be a good idea in the varchar.c and varlena.c calls,
but I'd be inclined to leave the rest of the calls alone.

			regards, tom lane