From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, David Zhang <david(dot)zhang(at)highgo(dot)ca> |
Cc: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Avoid unecessary MemSet call (src/backend/utils/cache/relcache.c) |
Date: | 2022-08-24 18:50:56 |
Message-ID: | 6c3e3577-0e44-5b40-b1b0-c56dbf8010f5@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 24.08.22 16:30, Alvaro Herrera wrote:
> On 2022-Aug-19, David Zhang wrote:
>> Should these obviously possible replacement of the standard library function
>> "memset" be considered as well? For example, something like the attached one
>> which is focusing on the pageinspect extension only.
>
> If you do this, you're creating a potential backpatching hazard. This
> is OK if we get something in return, so a question to ask is whether
> there is any benefit in doing it.
I don't follow how this is a backpatching hazard.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-08-24 19:00:10 | Re: Avoid unecessary MemSet call (src/backend/utils/cache/relcache.c) |
Previous Message | Peter Eisentraut | 2022-08-24 18:28:24 | Re: ICU for global collation |