| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 16 draft release notes ready |
| Date: | 2023-05-23 20:48:56 |
| Message-ID: | CAApHDvqnUoyrJxS4uqnKo87b3_cUjaDDte4NQag49YHu1oEOgA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 23 May 2023 at 06:04, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> On Mon, May 22, 2023 at 10:59:36AM -0700, Andres Freund wrote:
> > And here it's not just performance, but also memory usage, including steady
> > state memory usage.
>
> Understood. I continue to need help determining which items to include.
> Can you suggest some text? This?
>
> Improve efficiency of memory usage to allow for better scaling
Maybe something like:
* Reduce palloc() memory overhead for all memory allocations down to 8
bytes on all platforms. (Andres Freund, David Rowley)
This allows more efficient use of memory and is especially useful in
queries which perform operations (such as sorting or hashing) that
require more than work_mem.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2023-05-23 20:57:31 | Re: memory leak in trigger handling (since PG12) |
| Previous Message | David Rowley | 2023-05-23 20:37:45 | Re: PG 16 draft release notes ready |