public inbox for [email protected]  

help / color / mirror / Atom feed

From: Daniel Gustafsson <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Ranier Vilela <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Avoid use deprecated Windows Memory API
Date: Thu, 15 Sep 2022 15:30:13 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

> On 15 Sep 2022, at 15:13, Alvaro Herrera <[email protected]> wrote:
> 
> On 2022-Sep-15, Ranier Vilela wrote:
> 
>> Em qui., 15 de set. de 2022 às 09:50, Alvaro Herrera <
>> [email protected]> escreveu:
> 
>>> These functions you are patching are not in performance-sensitive code,
>>> so I doubt this makes any difference performance wise.  I doubt
>>> Microsoft will ever remove these deprecated functions, given its history
>>> of backwards compatibility, so from that perspective this change does
>>> not achieve anything either.
>> 
>> If users don't adapt to the new API, the old one will never really expire.
> 
> If you are claiming that Microsoft will remove the old API because
> Postgres stopped using it, ... sorry, no.

Also, worth noting is that these functions aren't actually deprecated.  The
note in the docs state:

	The local functions have greater overhead and provide fewer features
	than other memory management functions.  New applications should use
	the heap functions unless documentation states that a local function
	should be used.

And following the bouncing ball into the documentation they refer to [0] I read
this:

	As a result, the global and local families of functions are equivalent
	and choosing between them is a matter of personal preference.

--
Daniel Gustafsson		https://vmware.com/

[0]: https://docs.microsoft.com/en-us/windows/win32/memory/global-and-local-functions

view thread (13+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Avoid use deprecated Windows Memory API
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox