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 1m329A-0008Ha-3O for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Jul 2021 20:03:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m3297-0007Vr-VG for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Jul 2021 20:03:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m3297-0007Vj-Li for pgsql-hackers@lists.postgresql.org; Mon, 12 Jul 2021 20:03:17 +0000 Received: from wforward1-smtp.messagingengine.com ([64.147.123.30]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m3290-0002dl-AF for pgsql-hackers@lists.postgresql.org; Mon, 12 Jul 2021 20:03:16 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailforward.west.internal (Postfix) with ESMTP id D19631AC118A; Mon, 12 Jul 2021 16:03:06 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 12 Jul 2021 16:03:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=luo3j8F7EIkhHwkQRna3Dt1TGXwE3nuxr1XeY9gmy UQ=; b=hDB9k9GFCNbk2IaI9Uv/AHXLkHeE6emxZT765mpl0sl7cs6OJWW2EnWT4 iQFGmEXxIioQEngYVUjLvwLG2Qwbkw/xqRvHmr5gN+r7i/J3WiceUDwgSVfPCt0S 0cywysb8u3s7qubcVAq9tHfsG+CmuzPjh0Nf31M9l8RhvxsbuJMq1Vk8uoyMpwND NjBSsVVRjp9wBTyWcTFKs21xrMeM3WLwrVZYOSTlsB7UgE8/pYxiCPWqHQqOERHx XL/hbupzPh1aawVNOn204Po6LIQ/mOXTNmkjsiXnAAxR2/HZh1OQop0WRTQOqW25 z6SYBlygy+STVjSCIbAncp9xl+sDA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudefgddtgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuvfhfhffkffgfgggjtgfgsehtjeertddtfeehnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpefhfeelfeeuveduvdffheej tdejjefglefhtddvffehledutedugeeffedtffffjeenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 12 Jul 2021 16:03:01 -0400 (EDT) Subject: Re: Feature improvement: can we add queryId for pg_catalog.pg_stat_activity view? To: Julien Rouhaud , Fujii Masao Cc: Bruce Momjian , Alvaro Herrera , Tom Lane , Nitin Jadhav , Hannu Krosing , Robert Haas , Pavel Stehule , Michael Paquier , torikoshia , Atsushi Torikoshi , Tatsuro Yamada , Tomas Vondra , Evgeny Efimkin , PostgreSQL Hackers , Magnus Hagander References: <20210413021246.GD4231@momjian.us> <20210413173016.GA29955@alvherre.pgsql> <20210414183326.GA10946@momjian.us> <20210420162244.GD30205@momjian.us> <20210422092317.xnuvva2322dflxdm@nol> From: Peter Eisentraut Message-ID: <8f5e63b8-e8ed-0f80-d8c4-68222624c200@enterprisedb.com> Date: Mon, 12 Jul 2021 22:02:59 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210422092317.xnuvva2322dflxdm@nol> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 22.04.21 11:23, Julien Rouhaud wrote: > The statistics gathered by the module are made available via a > view named pg_stat_statements. This view > - contains one row for each distinct database ID, user ID and query > - ID (up to the maximum number of distinct statements that the module > + contains one row for each distinct database ID, user ID, query ID and > + toplevel (up to the maximum number of distinct statements that the module > can track). The columns of the view are shown in > . I'm having trouble parsing this new sentence. It now says essentially "This view contains one row for each distinct database ID, each distinct user ID, each distinct query ID, and each distinct toplevel." That last part doesn't make sense.