Re: PG 16 draft release notes ready - Mailing list pgsql-hackers

From Andres Freund
Subject Re: PG 16 draft release notes ready
Date
Msg-id 5749E807-A5B7-4CC7-8282-84F6F0D4D1D0@anarazel.de
Whole thread Raw
In response to Re: PG 16 draft release notes ready  ("Jonathan S. Katz" <jkatz@postgresql.org>)
Responses Re: PG 16 draft release notes ready
List pgsql-hackers
Hi,

On May 21, 2023 11:46:56 AM PDT, "Jonathan S. Katz" <jkatz@postgresql.org> wrote:
>On 5/21/23 1:13 PM, Andres Freund wrote:
>
>>
>> Looking through the release notes, I didn't see an entry for
>>
>> commit c6e0fe1f2a08505544c410f613839664eea9eb21
>> Author: David Rowley <drowley@postgresql.org>
>> Date:   2022-08-29 17:15:00 +1200
>>        Improve performance of and reduce overheads of memory management
>>
>> even though I think that's one of the more impactful improvements. What was
>> the reason for leaving that out?
>
>IIUC in[1], would this "just speed up" read-heavy workloads?

I don't think so. It can speed up write workloads as well. But more importantly it can noticeably reduce memory usage,
includingfor things like the relcache. 

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: createuser --memeber and PG 16
Next
From: Tom Lane
Date:
Subject: Re: Assert failure of the cross-check for nullingrels