From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: Avoid use deprecated Windows Memory API |
Date: | 2023-03-22 12:18:31 |
Message-ID: | CAEudQApivpubcRSQp1YrUJVFkQw2+Sak=fH7CYpB8Ndmdai07w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Em qua., 22 de mar. de 2023 às 07:01, Daniel Gustafsson <daniel(at)yesql(dot)se>
escreveu:
> > On 19 Mar 2023, at 23:41, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> >
> > On Fri, Mar 17, 2023 at 12:19:56PM -0300, Ranier Vilela wrote:
> >> Rebased to latest Head.
> >
> > I was looking at this thread, and echoing Daniel's and Alvaro's
> > arguments, I don't quite see why this patch is something we need. I
> > would recommend to mark it as rejected and move on.
>
> Unless the claimed performance improvement is measured and provides a
> speedup,
> and the loss of zeroing memory is guaranteed safe, there doesn't seem to be
> much value provided.
>
At no time was it suggested that there would be performance gains.
The patch proposes to adjust the API that the manufacturer asks you to use.
However, I see no point in discussing a defunct patch.
regards,
Ranier Vilela
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2023-03-22 12:18:46 | Re: SQL/JSON revisited |
Previous Message | Dave Cramer | 2023-03-22 12:18:25 | Re: Request for comment on setting binary format output per session |