Re: Avoid unecessary MemSet call (src/backend/utils/cache/relcache.c)
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Ranier Vilela <ranier.vf@gmail.com>, David Rowley <dgrowleyml@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2022-06-30T22:37:23Z
Lists: pgsql-hackers
On 19.05.22 18:09, Ranier Vilela wrote: > Taking it a step further. > Created a new patch into commitfest, targeting 16 version. > https://commitfest.postgresql.org/38/3645/ > <https://commitfest.postgresql.org/38/3645/> I have committed your 001 patch, which was clearly a (harmless) mistake. I have also committed a patch that gets rid of MemSet() calls where the value is a constant not-0, because that just falls back to memset() anyway. I'm on board with trying to get rid of MemSet(), but first I need to analyze all the performance numbers and arguments that were shown in this thread.
Commits
-
Replace many MemSet calls with struct initialization
- 9fd45870c143 16.0 landed
-
Change some unnecessary MemSet calls
- 258f48f858b0 16.0 landed
-
Avoid unnecessary MemSet call
- 8cd61d288adf 16.0 landed