pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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
Date: Mon, 11 May 2020 19:41:01 -0500
Message-ID: <20200512004101.GO18456@telsasoft.com> (raw)
In-Reply-To: <20200505031600.GB21752@momjian.us>
References: <20200505031600.GB21752@momjian.us>

|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





view thread (194+ messages)  latest in thread

Message-ID: <20200512004101.GO18456@telsasoft.com>
Permalink:  ../20200512004101.GO18456@telsasoft.com/
Also on:    postgresql.org/message-id/20200512004101.GO18456@telsasoft.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, bruce@momjian.us
  Subject: Re: PG 13 release notes, first draft
  In-Reply-To: <20200512004101.GO18456@telsasoft.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox