Re: PG 16 draft release notes ready

From: Andres Freund <andres(at)anarazel(dot)de>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 16 draft release notes ready
Date: 2023-05-21 19:24:31
Message-ID: 5749E807-A5B7-4CC7-8282-84F6F0D4D1D0@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On May 21, 2023 11:46:56 AM PDT, "Jonathan S. Katz" <jkatz(at)postgresql(dot)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(at)postgresql(dot)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, including for things like the relcache.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-05-21 19:44:43 Re: Assert failure of the cross-check for nullingrels
Previous Message Nathan Bossart 2023-05-21 19:16:58 Re: createuser --memeber and PG 16