On Mon, May 22, 2023 at 10:59:36AM -0700, Andres Freund wrote:
> On 2023-05-21 22:46:58 -0400, Bruce Momjian wrote:
> > > For the above two items, I mention items that would change user
> > > like new features or changes that are significant enough that they would
> > > change user behavior. For example, if a new join method increases
> > > performance by 5x, that could change user behavior. Based on the quoted
> > > numbers above, I didn't think "hash now faster" would be appropriate to
> > > mention. Right?
>
> I continue, as in past releases, to think that this is a bad policy. For
> existing workloads performance improvements are commonly a more convincing
> reason to upgrade than new features - they allow users to scale the workload
> further, without needing application changes.
>
> Of course there are performance improvement that are too miniscule to be worth
> mentioning, but it's not a common case.
>
> 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
--
Bruce Momjian <br...@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
