Date: Mon, 11 May 2020 19:41:01 -0500
From: Justin Pryzby <pryzby@telsasoft.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: PG 13 release notes, first draft
Message-ID: <20200512004101.GO18456@telsasoft.com>
References: <20200505031600.GB21752@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20200505031600.GB21752@momjian.us>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

|Allow function call backtraces of errors to be logged (Peter Eisentraut, Álvaro Herrera)
|Server variable backtrace_functions specifies which C functions should generate backtraces on error.

I think the details in the description are eclipsing the most important thing:
backtraces on Assert().  I would say "Support for showing backtraces on error".

Regarding this one:
|Add system view pg_shmem_allocations to display shared memory usage (Andres Freund, Robert Haas)
|WHAT IS THE ENTRY WITH NO NAME?

There seems to be two special, "unnamed" cases:
src/backend/storage/ipc/shmem.c-        /* output shared memory allocated but not counted via the shmem index */
src/backend/storage/ipc/shmem.c:        values[0] = CStringGetTextDatum("<anonymous>");
...
src/backend/storage/ipc/shmem.c-        /* output as-of-yet unused shared memory */
src/backend/storage/ipc/shmem.c-        nulls[0] = true;

That seems to be adequately documented:
https://www.postgresql.org/docs/devel/view-pg-shmem-allocations.html
|NULL for unused memory and <anonymous> for anonymous allocations.

I would remove this part:
"Previously, this could only be set at server start."

-- 
Justin