pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Pavel Luzanov <p.luzanov@postgrespro.ru>
To: Melanie Plageman <melanieplageman@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: tgl@sss.pgh.pa.us, vignesh21@gmail.com, lukas@fittl.com, alvherre@alvh.no-ip.org, magnus@hagander.net, pgsql-hackers@postgresql.org, thomas.munro@gmail.com, m.sakrejda@gmail.com, Michael Paquier <michael@paquier.xyz>
Subject: Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)
Date: Tue, 25 Apr 2023 10:16:05 +0300
Message-ID: <892d6d93-bc91-7f9a-0dbb-bed8cb29c31e@postgrespro.ru> (raw)
In-Reply-To: <CAAKRu_bkaOTdnuTw73Mf5A1ZSq5ZMcmHBvZr29ivwpaSVsvgWw@mail.gmail.com>
References: <20230306.152425.316894602450485455.horikyota.ntt@gmail.com>
	<CAAKRu_ZRKp-zDCSVk9p8XE=ZKTn3WiJD6Mt=n=eSPQ7Kg-=HRw@mail.gmail.com>
	<20230306190919.ai6mxdq3sygyyths@awork3.anarazel.de>
	<20230306192409.daz5ivq4mbbr2ye7@liskov>
	<20230306193404.3btuacgc6um33mt2@awork3.anarazel.de>
	<CAAKRu_ZmAhCGzk2GkNeMHTu0Oh=rtNKU7Q+fkzLs-PZBp1sicg@mail.gmail.com>
	<20230307181844.hxnlfi3wa5lm7sm2@awork3.anarazel.de>
	<ZAnWU8WbXEDjrfUE@telsasoft.com>
	<20230309194301.mjdddcoswgr6xoxa@awork3.anarazel.de>
	<ZAuQuBQa7eKAITeA@telsasoft.com>
	<CAAKRu_YHKj73MjgTLZUraQ72VFm=CWg14Dp0BDbsM5YUgWG89Q@mail.gmail.com>
	<fcbe2851-f1fb-9863-54bc-a95dc7a0d946@postgrespro.ru>
	<CAAKRu_bk1LTUezVwTO+NLcXp9TTmLtdUnmFHskzniNo6ThqxvQ@mail.gmail.com>
	<d9913624-9cb1-d238-21f7-266f0a1eef82@postgrespro.ru>
	<CAAKRu_ZKYT=FMV2OME5J7Da1roD4cBOiRho3RCu1rNYN98hbtA@mail.gmail.com>
	<beccfab0-8142-1526-c219-2e8352977629@postgrespro.ru>
	<CAAKRu_bkaOTdnuTw73Mf5A1ZSq5ZMcmHBvZr29ivwpaSVsvgWw@mail.gmail.com>

On 24.04.2023 23:53, Melanie Plageman wrote:
> I copied the committer who most recently touched pg_stat_io (Michael
> Paquier) to see if we could get someone interested in committing this
> docs update.

I can explain my motivation by suggesting this update.

pg_stat_io is a very impressive feature. So I decided to try it.
I see 4 rows for some 'standalone backend'  out of 30 total rows of the 
view.

The attempt to find description of 'standalone backend' in the docs
did not result in anything. pg_stat_io page references pg_stat_activity
for backend types. But pg_stat_activity page doesn't say anything
about 'standalone backend'.

I think this question will be popular without clarifying in docs.

-- 
Pavel Luzanov
Postgres Professional: https://postgrespro.com






view thread (173+ messages)

Message-ID: <892d6d93-bc91-7f9a-0dbb-bed8cb29c31e@postgrespro.ru>
Permalink:  ../892d6d93-bc91-7f9a-0dbb-bed8cb29c31e@postgrespro.ru/
Also on:    postgresql.org/message-id/892d6d93-bc91-7f9a-0dbb-bed8cb29c31e@postgrespro.ru

 · 

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: p.luzanov@postgrespro.ru, melanieplageman@gmail.com, pryzby@telsasoft.com, andres@anarazel.de, horikyota.ntt@gmail.com, michael@paquier.xyz
  Subject: Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)
  In-Reply-To: <892d6d93-bc91-7f9a-0dbb-bed8cb29c31e@postgrespro.ru>

* 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