Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nNDAJ-0008Hg-KZ for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Feb 2022 12:24:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nNDAI-0007mM-Ff for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Feb 2022 12:24:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nNDAI-0007mD-6M for pgsql-hackers@lists.postgresql.org; Thu, 24 Feb 2022 12:24:10 +0000 Received: from [66.111.4.28] (helo=out4-smtp.messagingengine.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nNDAD-000058-LD for pgsql-hackers@postgresql.org; Thu, 24 Feb 2022 12:24:09 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id ADD685C112C; Thu, 24 Feb 2022 07:23:57 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 24 Feb 2022 07:23:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=RelSzQY4PgWt+GUx7EqntdZ29WrDsR7RwD/DRxC3c rc=; b=DqPKhHmbJyw0yG6V8YXn/nnUUFx6//XhOYq2/s4DrhKbSbi1ZKv632hc6 RonNUOMOMN+gYKCYheogpqju8jI8smSTwAxbBFf65Onhy7gVDKHp5ooKzyf01wOv igT1D0TOeIzppHJ2tuv/6QnUChDXsNsJB1+0Z7/auPkpYsjzQt494cOWl19znJev lG7V28Cc8kEiP9WGAO/oSNfwBOjH6bjl4mojCpOgmPk9V54LPw2GyYtyMo1bt8aY 8mK9yGtmIQzt3dkI4ZWhC5ZTTF3kBCctr4ebfq4o+Mv2hxg5GK7uK2rlVUnoP4xM GaeYFdy/CvTuBy80HZgO8O+dr5Jng== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrledvgdeflecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 24 Feb 2022 07:23:56 -0500 (EST) Message-ID: Date: Thu, 24 Feb 2022 13:23:55 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.0 Subject: Re: Design of pg_stat_subscription_workers vs pgstats Content-Language: en-US To: Masahiko Sawada Cc: Peter Smith , Amit Kapila , Andres Freund , "David G. Johnston" , pgsql-hackers References: <20220215182641.2cejma6tcgeoqyw2@alap3.anarazel.de> <20220218203255.d3evl6qi2n6gxy6b@alap3.anarazel.de> <20220219160203.y5w2ktc2utthn7pe@alap3.anarazel.de> <20220221053453.lo6fzmji23ennvgj@alap3.anarazel.de> <20220221074806.nyhdberpuwbcbudp@alap3.anarazel.de> <6f7701b0-ce5c-d01c-18f2-5de3a02ff6b6@enterprisedb.com> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 66.111.4.28 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 24.02.22 12:46, Masahiko Sawada wrote: >> We have a view called pg_stat_activity, which is very well known. From >> that perspective, "activity" means what is happening right now or what >> has happened most recently. The reworked view in this patch does not >> contain that (we already have pg_stat_subscription for that), but it >> contains accumulated counters. > Right. > > What pg_stat_subscription shows is rather suitable for the name > pg_stat_subscription_activity than the reworked view. But switching > these names would also not be a good idea. I think it's better to use > "subscription" in the view name since it shows actually statistics for > subscriptions and subscription OID is the key. I personally prefer > pg_stat_subscription_counters among the ideas that have been proposed > so far, but I'd like to hear opinions and votes. _counters will fail if there is something not a counter (such as last-timestamp-of-something). Earlier, pg_stat_subscription_stats was mentioned, which doesn't have that problem.