| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Avoid use deprecated Windows Memory API |
| Date: | 2022-09-15 13:13:47 |
| Message-ID: | 20220915131347.fjijnfmafcua7m3d@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-Sep-15, Ranier Vilela wrote:
> Em qui., 15 de set. de 2022 às 09:50, Alvaro Herrera <
> alvherre(at)alvh(dot)no-ip(dot)org> 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.
> Neither the patch nor the thread deals with palloc.
I know. Which is why I think the patch is useless.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2022-09-15 13:19:26 | Re: Avoid use deprecated Windows Memory API |
| Previous Message | Alvaro Herrera | 2022-09-15 13:11:24 | Re: Avoid use deprecated Windows Memory API |