Re: First draft of the PG 15 release notes

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: First draft of the PG 15 release notes
Date: 2022-05-11 02:31:08
Message-ID: CAApHDvo57tuCk=L_=_Q0mvmBxUYi+aoZZ6HtxmYM9cg7euX_KA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 11 May 2022 at 14:02, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> On Wed, May 11, 2022 at 12:39:41PM +1200, David Rowley wrote:
> > I think the sort improvements done in v15 are worth a mention under
> > General Performance. The commits for this were 91e9e89dc, 40af10b57
> > and 697492434. I've been running a few benchmarks between v14 and v15
> > over the past few days and a fairly average case speedup is about 25%.
> > but there are cases where I've seen up to 400%. I think the increase
> > is to an extent that we maybe should have considered making tweaks in
> > cost_tuplesort(). I saw some plans that ran in about 60% of the time
> > by disabling Hash Agg and allowing Sort / Group Agg to do the work.
>
> Good point. Do you have any suggested text? I can't really see it
> clearly based on the commits, except "sorting is faster".

If we're going to lump those into a single line then maybe something
along the lines of:

* Reduce memory consumption and improve performance of sorting tuples in memory

I think one line is fine from a user's perspective, but it's slightly
harder to know the order of the names in the credits given the 3
independent commits.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message osumi.takamichi@fujitsu.com 2022-05-11 02:32:36 RE: Data is copied twice when specifying both child and parent table in publication
Previous Message Michael Paquier 2022-05-11 02:18:29 Re: make MaxBackends available in _PG_init