| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, 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 23:51:50 |
| Message-ID: | 1fd256d6-fac6-c10b-42d4-66ca8c2f2c8f@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/21/23 3:24 PM, Andres Freund wrote:
> 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.
Cool! I'll dive more into the thread later to learn more.
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2023-05-21 23:53:38 | Re: PG 16 draft release notes ready |
| Previous Message | Andres Freund | 2023-05-21 22:14:23 | Re: pg_stat_io for the startup process |