Re: fix memcpy() overlap

Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Isn't memmove() for overlaping regions?  That's what my BSD manual page
> says.

If we want to get rid of the valgrind warning, a simpler patch would be
to substitute memmove for memcpy in that particular numeric.c subroutine
(at least, I assume this will shut valgrind up).  I could live with that;
it seems a less intrusive fix than a special-case test that will hardly
ever trigger.

            regards, tom lane