Re: PG 14 release notes, first draft

From: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 14 release notes, first draft
Date: 2021-09-27 01:07:13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Mon, 10 May 2021 02:03:08 -0400
Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> I have committed the first draft of the PG 14 release notes. You can
> see the most current build of them here:
> I need clarification on many items, and the document still needs its
> items properly ordered, and markup added. I also expect a lot of
> feedback.

I found that there isn't an item that referring the following commit:

commit 547f04e7348b6ed992bd4a197d39661fe7c25097
Author: Thomas Munro <tmunro(at)postgresql(dot)org>
Date: Wed Mar 10 16:09:50 2021 +1300

pgbench: Improve time logic.

Instead of instr_time (struct timespec) and the INSTR_XXX macros,
introduce pg_time_usec_t and use integer arithmetic. Don't include the
connection time in TPS unless using -C mode, but report it separately.

This commit changed the output results that are visible for users, that is,
tps with "including connection establishing" and "excluding ..." are no
longer reported, so I wonder we should let users know it.

Another user-visible change on pgbench that is not listed in the release
notes is the support for pipeline mode. There is a mention about libpq
supporting pipeline, so I think we can also mention that of pgbench.

There are other minor improvement on pgbench, but pgbench is just a
benchnark tool and its changes do not directly affect to user application,
so maybe we don't have to describe all in the release notes.

Yugo Nagata

Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ajin Cherian 2021-09-27 01:20:12 Re: extensible options syntax for replication parser?
Previous Message Jaime Casanova 2021-09-27 00:52:09 Re: Evaluate expression at planning time for two more cases