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 1um8Yo-00AUHs-Eb for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Aug 2025 10:18:22 +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 1um8Ym-00EOil-Tl for pgsql-bugs@arkaria.postgresql.org; Wed, 13 Aug 2025 10:18:21 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um8AR-00E9WQ-Ok for pgsql-bugs@lists.postgresql.org; Wed, 13 Aug 2025 09:53:12 +0000 Received: from zg8tmja2lje4os4yms4ymjma.icoremail.net ([206.189.21.223]) by makus.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1um8AK-000LEa-0y for pgsql-bugs@lists.postgresql.org; Wed, 13 Aug 2025 09:53:10 +0000 Received: from sunwoda-evb.com (unknown [119.146.89.130]) by hzbj-forward-1.icoremail.net (Coremail) with SMTP id AQAAfwB3tLt4YJxoRIADAA--.7248S2; Wed, 13 Aug 2025 17:52:56 +0800 (CST) Received: from sunwoda-evb.com (unknown [172.27.103.90]) by mtasvr (Coremail) with SMTP id _____wDHGNh2YJxobBQMAA--.19700S3; Wed, 13 Aug 2025 17:52:54 +0800 (CST) Received: from DL000951 (unknown [172.27.103.90]) by evbmailapp02 (Coremail) with SMTP id 3PEbrAAX5vN1YJxoZ7g2AA--.5913S2; Wed, 13 Aug 2025 17:52:53 +0800 (CST) From: "zhouenbing" To: References: In-Reply-To: Subject: =?gb2312?B?tPC4tDogRW1wdHkgcXVlcnlfaWQgaW4gcGdfc3RhdF9hY3Rpdml0eQ==?= Date: Wed, 13 Aug 2025 17:52:53 +0800 Message-ID: <000501dc0c38$09b76cb0$1d264610$@sunwoda-evb.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01DC0C7B.17DB21E0" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdwMN7PXXMHGuexwRAG7eOFbOlZv7gAAEyMA Content-Language: zh-cn X-CM-TRANSID: 3PEbrAAX5vN1YJxoZ7g2AA--.5913S2 X-CM-SenderInfo: 52kr3vxqel0ww6vx045rgdgv1yeou0bp/ Authentication-Results: hzbj-forward-1.icoremail.net; spf=softfail smt p.mail=zhouenbing@sunwoda-evb.com; X-Coremail-Antispam: 1UD129KBjvdXoWrtw4rKw1xAF1fCrWfuF4Durg_yoW3tFg_Wa ykWr9rt34UXw4DWws5Gr4UZFZ3Xayjg34kGws5Xw18JFyxZwsxWFs7G3y7Gwn7Jrs5Kr9x KFW3Xw1Sva4rWjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbqAYFVCjjxCrM7AC8VAFwI0_Jr0_Gr1l1IIY67AEw4v_JrI_Jryl 8cAvFVAK0II2c7xJM28CjxkF64kEwVA0rcxSw2x7M28EF7xvwVC0I7IYx2IY67AKxVWDJV Cq3wA2z4x0Y4vE2Ix0cI8IcVCY1x0267AKxVW8Jr0_Cr1UM28EF7xvwVC2z280aVAFwI0_ GcCE3s1l84ACjcxK6I8E87Iv6xkF7I0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEnc xIr21l5I8CrVAYj202j2C_Gr0_Xr1l5I8CrVAqjxCE14ACF2xKxwAqx4xG64kEw2xG04xI wI0_Jr0_Gr1l5I8CrVCF0I0E4I0vr24lYx0E2Ix0cI8IcVAFwI0_ZF0_GryDMcIj6I8E87 Iv67AKxVWYoVW2owAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41l7480Y4vE I4kI2Ix0rVAqx4xJMx02cVAKzwCY02Avz4vE14v_GFWlc2IjII80xcxEwVAKI48JMxvI42 IY6xIIjxv20xvE14v26r1j6r1xMxvI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lcIIF 0xvEx4A2jsIE14v26r1j6r4UMxvI42IY6I8E87Iv6xkF7I0E14v26r1j6r4UMxAIw28Icx kI7VAKI48JMxCjnVCFn7xvrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v2 6r106r1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jr0_JrylIxkGc2 Ij64vIr41lIxAIcVCF04k26cxKx2IYs7xG6Fyj6rWUJbIYCTnIWIevJa73UjIFyTuYvjxU DWrWDUUUU 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_0006_01DC0C7B.17DB21E0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Maile address: https://www.postgresql.org/message-id/ed81b882-2bef-47e8-95af-3a55ddf28e1= 8@e wie.name =20 =B7=A2=BC=FE=C8=CB: zhouenbing [mailto:zhouenbing@sunwoda-evb.com]=20 =B7=A2=CB=CD=CA=B1=BC=E4: 2025-08-13 17:50 =CA=D5=BC=FE=C8=CB: 'pgsql-bugs@lists.postgresql.org' = =D6=F7=CC=E2: Empty query_id in pg_stat_activity =20 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_0006_01DC0C7B.17DB21E0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Maile = address: = https://www.postgresql.org/message-id/ed81b882-2bef-47e8-95af-3a55ddf28e1= 8@ewie.name

 

=B7=A2=BC=FE=C8=CB: zhouenbing = [mailto:zhouenbing@sunwoda-evb.com]
=B7=A2=CB=CD=CA=B1=BC=E4: 2025-08-13 17:50
=CA=D5=BC=FE=C8=CB: 'pgsql-bugs@lists.postgresql.org' = <pgsql-bugs@lists.postgresql.org>
=D6=F7=CC=E2: Empty query_id in = pg_stat_activity

 

I see that the Message ID is' ae6ef509-7= bba-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_0006_01DC0C7B.17DB21E0--