pgsql: Use plain memset() in numeric.c, not MemSet and friends. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Use plain memset() in numeric.c, not MemSet and friends.
Date
Msg-id E1kFfqT-00035m-4V@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Use plain memset() in numeric.c, not MemSet and friends.

This essentially reverts a micro-optimization I made years ago,
as part of the much larger commit d72f6c750.  It's doubtful
that there was any hard evidence for it being helpful even then,
and the case is even more dubious now that modern compilers
are so much smarter about inlining memset().

The proximate reason for undoing it is to get rid of the type punning
inherent in MemSet, for fear that that may cause problems now that
we're applying additional optimization switches to numeric.c.
At the very least this'll silence some warnings from a few old
buildfarm animals.

(It's probably past time for another look at whether MemSet is still
worth anything at all, but I do not propose to tackle that question
right now.)

Discussion: https://postgr.es/m/CAJ3gD9evtA_vBo+WMYMyT-u=keHX7-r8p2w7OSRfXf42LTwCZQ@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/3438c988fd757c74ea4ddd80cdbb7405f4a1bc39

Modified Files
--------------
src/backend/utils/adt/numeric.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Use for name of unnamed portal's memory context
Next
From: Andres Freund
Date:
Subject: pgsql: Fix autovacuum cancellation.