Skip site navigation (1) Skip section navigation (2)

Re: fix memcpy() overlap

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>,PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: fix memcpy() overlap
Date: 2004-02-04 01:04:22
Message-ID: 87llnj64fd.fsf@mailbox.samurai.com (view raw or flat)
Thread:
Lists: pgsql-patches
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> If we want to get rid of the valgrind warning, a simpler patch would
> be to substitute memmove for memcpy

I've made this change and committed it to HEAD.

-Neil


In response to

pgsql-patches by date

Next:From: Claudio NatoliDate: 2004-02-04 03:32:50
Subject: Re: New win32 signals patch (3)
Previous:From: Andrew DunstanDate: 2004-02-04 01:03:42
Subject: Re: log session end - again

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group