As the article demonstrated, performance of memove libraries is dependent on
the size of memory copied and the hardware. Therefore it is both a software
and hardware function.
This post was simply put out here as something that might be of use. It is
Ok if it is of no interest.
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tom Lane
Sent: 07 July 2016 18:02
To: Stephen Frost <sfrost@snowman.net>
Cc: Merlin Moncure <mmoncure@gmail.com>; FarjadFarid(ChkNet)
<farjad.farid@checknetworks.com>; Alvaro Herrera <alvherre@2ndquadrant.com>;
PostgreSQL General <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] Fastest memmove in C
Stephen Frost <sfrost@snowman.net> writes:
> While I agree with this, I'm trying to figure out why this isn't being
> incorporated into glibc instead..?
Indeed --- it seems far more useful to integrate this sort of work at the
libc level than to ask applications to support their own replacements for
libc routines.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general