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 1nNAoL-0002Iq-EB for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Feb 2022 09:53:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nNAoJ-00054y-Np for pgsql-hackers@arkaria.postgresql.org; Thu, 24 Feb 2022 09:53:19 +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 1nNAoJ-0004x9-Ce for pgsql-hackers@lists.postgresql.org; Thu, 24 Feb 2022 09:53:19 +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 1nNAoG-0007IR-QS for pgsql-hackers@postgresql.org; Thu, 24 Feb 2022 09:53:18 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id AEA215C0956; Thu, 24 Feb 2022 04:53:04 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Thu, 24 Feb 2022 04:53:04 -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=qSEybf4b5LzwcGAmej8FKX/0kdYp83VhbkGDcGteQ ME=; b=oRpdU3e+ulHSUGBH/0RFEj1ho/nUwoDy34DD+G6Xtmbs3q15nWz/Nydee rZQAkQk9lG6wksY6odASkIDCv04L1YIq7Hhgy9z/wQaE72Sklx/kI4eyoDnFgMOx BowUR5RowvY6lCRtyWkQO+c3+rD/X/s/bZ0rmZNycr8VsFivrcemEmN/v3UDML5b D//yD3Xt43FSmtG92TZeaDSSTxNLuhtFPKfe4svkOGuyd/Q1x4Qadkk5dfDTDc5p btfP17TuDOIBcHhb/qPRgKHl59P2O4JE/96lNOzBlgT8F6K1hVXLUf5uSD23DHu9 y+c9ovb5lgz03e2aixRCgAh2lhDfg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrledvgddtkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 24 Feb 2022 04:53:03 -0500 (EST) Message-ID: <6f7701b0-ce5c-d01c-18f2-5de3a02ff6b6@enterprisedb.com> Date: Thu, 24 Feb 2022 10:53:02 +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 , Peter Smith Cc: 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> 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 02:32, Masahiko Sawada wrote: > On Wed, Feb 23, 2022 at 12:08 PM Peter Smith wrote: >> >> Hi. Below are my review comments for the v1 patch. > > Thank you for the comments! I've attached the latest version patch > that incorporated all comments I got so far. The primary change from > the previous version is that the subscription statistics live globally > rather than per-database. I don't think the name pg_stat_subscription_activity is a good choice. 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.