On 05.04.2023 03:41, Melanie Plageman wrote:
On Tue, Apr 4, 2023 at 4:35 PM Pavel Luzanov <p.luza...@postgrespro.ru> wrote:
After a little thought... I'm not sure about the term 'bootstrap
process'. I can't find this term in the documentation.
There are various mentions of "bootstrap" peppered throughout the docs
but no concise summary of what it is. For example, initdb docs mention
the "bootstrap backend" [1].
Interestingly, 910cab820d0 added "Bootstrap superuser" in November. This
doesn't really cover what bootstrapping is itself, but I wonder if that
is useful? If so, you could propose a glossary entry for it?
(preferably in a new thread)
I'm not sure if this is the reason for adding a new entry in the glossary.
Do I understand correctly that this is a postmaster? If so, then the
postmaster process is not shown in pg_stat_activity.
No, bootstrap process is for initializing the template database. You
will not be able to see pg_stat_activity when it is running.
Oh, it's clear to me now. Thank you for the explanation.
You can query pg_stat_activity from single user mode, so it is relevant
to pg_stat_activity also. I take your point that bootstrap mode isn't
relevant for pg_stat_activity, but I am hesitant to add that distinction
to the pg_stat_io docs since the reason you won't see it in
pg_stat_activity is because it is ephemeral and before a user can access
the database and not because stats are not tracked for it.
Can you think of a way to convey this?
See my attempt attached.
I'm not sure about the wording. But I think we can avoid the term
'bootstrap process'
by replacing it with "database cluster initialization", which should be
clear to everyone.
--
Pavel Luzanov
Postgres Professional: https://postgrespro.com
From ff76b81a9d52581f6fdaf9c1f3885e8272d2ae3c Mon Sep 17 00:00:00 2001
From: Pavel Luzanov <p.luza...@postgrespro.ru>
Date: Mon, 10 Apr 2023 10:25:52 +0300
Subject: [PATCH v2] [PATCH v2] Document standalone backend type in
pg_stat_activity
Reported-by: Pavel Luzanov <p.luza...@postgrespro.ru>
Discussion: https://www.postgresql.org/message-id/fcbe2851-f1fb-9863-54bc-a95dc7a0d946%40postgrespro.ru
---
doc/src/sgml/monitoring.sgml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 3f33a1c56c..45e20efbfb 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -991,6 +991,9 @@ postgres 27093 0.0 0.0 30096 2752 ? Ss 11:34 0:00 postgres: ser
<literal>archiver</literal>,
<literal>startup</literal>, <literal>walreceiver</literal>,
<literal>walsender</literal> and <literal>walwriter</literal>.
+ The special type <literal>standalone backend</literal> is used
+ when initializing a database cluster by <xref linkend="app-initdb"/>
+ and when running in the <xref linkend="app-postgres-single-user"/>.
In addition, background workers registered by extensions may have
additional types.
</para></entry>
--
2.34.1
