Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um8Vj-00ATUq-8l for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Aug 2025 10:15:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1um8Vh-00ELmk-H8 for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Aug 2025 10:15:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um886-00E74L-Ot for pgsql-bugs@lists.postgresql.org; Wed, 13 Aug 2025 09:50:46 +0000 Received: from azure-sdnproxy.icoremail.net ([52.237.72.81]) by magus.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1um880-000VpX-1A for pgsql-bugs@lists.postgresql.org; Wed, 13 Aug 2025 09:50:45 +0000 Received: from sunwoda-evb.com (unknown [119.146.89.130]) by hzbj-forward-1.icoremail.net (Coremail) with SMTP id AQAAfwC39bzqX5xo+38DAA--.8201S2; Wed, 13 Aug 2025 17:50:34 +0800 (CST) Received: from sunwoda-evb.com (unknown [172.27.103.90]) by mtasvr (Coremail) with SMTP id _____wCHlunnX5xoQRQMAA--.28535S3; Wed, 13 Aug 2025 17:50:32 +0800 (CST) Received: from DL000951 (unknown [172.27.103.90]) by evbmailapp01 (Coremail) with SMTP id 2_EbrAAnxN7lX5xoqmw2AA--.36931S2; Wed, 13 Aug 2025 17:50:30 +0800 (CST) From: "zhouenbing" To: Subject: Empty query_id in pg_stat_activity Date: Wed, 13 Aug 2025 17:50:29 +0800 Message-ID: <000001dc0c37$b4aa8180$1dff8480$@sunwoda-evb.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01DC0C7A.C2CE0FA0" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdwMN7PXXMHGuexwRAG7eOFbOlZv7g== Content-Language: zh-cn X-CM-TRANSID: 2_EbrAAnxN7lX5xoqmw2AA--.36931S2 X-CM-SenderInfo: 52kr3vxqel0ww6vx045rgdgv1yeou0bp/ Authentication-Results: hzbj-forward-1.icoremail.net; spf=softfail smt p.mail=zhouenbing@sunwoda-evb.com; X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUUYC7kC6x804xWl14x267AKxVWUJVW8JwAF IxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK021l84ACjcxK6x IIjxv20xvE14v26w1j6s0DM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4UJVWxJr1l84AC jcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_GcCE3s1le2I262 IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG67k08I80eVW8JVW5JwAqx4xG6c804VAFz4xC04v7 Mc02F40Ew4AK048IF2xKxVW8JVW5JwAqx4xG6xAIxVCFxsxG0wAv7VC0I7IYx2IY67AKxV W3AVW8Xw1lYx0Ex4A2jsIE14v26rkl6F8dMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvY 0x0EwIxGrwCjxxvEw4Wlc2xSY4AK67AK6r4fMxkI7II2jI8vz4vEwIxGrwCYIxAIcVC0I7 IYx2IY67AKxVWUJVWUCwCYIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMxvI42IY6I8E 87Iv67AKxVWUJVW8JwCYIxAIcVC2z280aVCY1x0267AKxVWUJVW8JwCF04k20xvY0x0EwI xGrwCF72vE42k0Y41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUGVWU WwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1j6r15MIIYrxkI7VAKI4 8JMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DYxBIdaVFxhVjvjDU0xZFpf9x07bUKsbU UUUU= List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_0001_01DC0C7A.C2CE0FA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I see that the Message ID is' ae6ef509-7bba-4d5b-aac4-82def6797e61@ewie.name The email states that the bug with an empty query_id has been fixed in versions 14.14/15.9/16.5/17.1. However, when I tested versions 15.4/15.9/17.4 using the pebench-M=simple | extended tool, I still encountered the issue of an empty query_id. This has caused some related problems in tracking performance issues on Postgres. Is this a testing problem or is the bug indeed present? ------=_NextPart_000_0001_01DC0C7A.C2CE0FA0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I see that the Message ID is' = ae6ef509-7bba-4d5b-aac4-82def6797e61@ewie.name The email states that the = bug with an empty query_id has been fixed in versions = 14.14/15.9/16.5/17.1. However, when I tested versions 15.4/15.9/17.4 = using the pebench-M=3Dsimple | extended tool, I still encountered the = issue of an empty query_id. This has caused some related problems in = tracking performance issues on Postgres. Is this a testing problem or is = the bug indeed present?

------=_NextPart_000_0001_01DC0C7A.C2CE0FA0--