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 1kRzdn-0004Yy-5u for pgsql-bugs@arkaria.postgresql.org; Mon, 12 Oct 2020 15:21:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kRzdl-0002qU-US for pgsql-bugs@arkaria.postgresql.org; Mon, 12 Oct 2020 15:21:33 +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 1kRzdl-0002qN-OP for pgsql-bugs@lists.postgresql.org; Mon, 12 Oct 2020 15:21:33 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kRzdj-000370-Ho for pgsql-bugs@lists.postgresql.org; Mon, 12 Oct 2020 15:21:33 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09CFLSGS3100750; Mon, 12 Oct 2020 11:21:28 -0400 From: Tom Lane To: axgrech@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16667: COMMIT AND CHAIN does not udpates database metrics ie. xact_commit In-reply-to: <16667-f86da4a2ede6435f@postgresql.org> References: <16667-f86da4a2ede6435f@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 12 Oct 2020 13:55:20 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3100748.1602516088.1@sss.pgh.pa.us> Date: Mon, 12 Oct 2020 11:21:28 -0400 Message-ID: <3100749.1602516088@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > We have an application that uses a new feature COMMIT AND CHAIN, the > application works generaly OK, but we have noticed that the pg_stat_database > (xact_commit/xact_rollback) are not updated, as they are if we used > BEGIN/COMMIT/BEGIN. I can't reproduce that here. Indeed, in a quick check I'd say the opposite: it looks like xact_commit advances twice where I'd only have expected it to advance once. regards, tom lane