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.96) (envelope-from ) id 1wPnlM-0012TQ-2c for pgsql-bugs@arkaria.postgresql.org; Wed, 20 May 2026 20:43:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wPnlK-008Usk-27 for pgsql-bugs@arkaria.postgresql.org; Wed, 20 May 2026 20:43:31 +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.96) (envelope-from ) id 1wPd9r-006u5Q-2x for pgsql-bugs@lists.postgresql.org; Wed, 20 May 2026 09:24:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wPd9p-00000000Wd1-38of for pgsql-bugs@lists.postgresql.org; Wed, 20 May 2026 09:24:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=KIf7itZVu3XewjzUxCT/MuRv/FhkwEIwxo6/AQyttTI=; b=P08yoIfm4y9rLCZmByxlwee1b5 EU68Gb2yEtXGwMdrZofqRhksgUSFAxiiKZYGeK0r7rPkVzgErdbxnQPmZfTge+7TchDKeoWH9C4OM TiH6Ufi8wX5t89t/zVEKevu+ePe6lq973s8PdvLq4uwWBEA13Z/4wXPPrB3QkUOaSk8nKtRkrWuZD TBOa6JPlmqfPIIOo07jZyMZnlqpmoXr6edK2PhLagC6PgkXD2lyDMGNx/xCrRJV5pFV5J8ENxomWC HU9qOm0X/Dzx3vUv2D1+O4DuqleOKL8Vf3W2JQG27P3sCD3AIQKLWrTChbyXEBf1Mkg8sAVK7kydN v0Ec5kTg==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wPd9n-001OZt-0I for pgsql-bugs@lists.postgresql.org; Wed, 20 May 2026 09:24:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wPd9m-002qo9-2G for pgsql-bugs@lists.postgresql.org; Wed, 20 May 2026 09:24:02 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: siddharth.gupta@nutanix.com Reply-To: siddharth.gupta@nutanix.com, pgsql-bugs@lists.postgresql.org Date: Wed, 20 May 2026 09:23:35 +0000 Message-ID: <19489-c0714e0a647fbe05@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19489 Logged by: Siddharth Gupta Email address: siddharth.gupta@nutanix.com PostgreSQL version: 18.4 Operating system: All Description: =20 Hi Team, We observed a potential function name conflict between TimescaleDB and pg_stat_monitor during extension compatibility and upgrade validation. Details observed: PostgreSQL Version: All versions TimescaleDB Version: all versions pg_stat_monitor Version: All versions The common function/object identified is: Function Name: histogram Issue observed: When both extensions are present in the same database, the shared function name appears to create a conflict during extension operations. Specifically, this issue prevents pg_stat_monitor from successfully completing the ALTER EXTENSION UPDATE operation. The upgrade fails due to the conflicting histogram function definition/object resolution between the two extensions. Current observations: Individual installation and upgrade of each extension works as expected. The issue is reproducible only when both TimescaleDB and pg_stat_monitor coexist in the same cluster/database. The failure is observed during pg_stat_monitor extension upgrade execution. Reproducible Steps: Install PostgreSQL Create extension TimescaleDB Create extension pg_stat_monitor(older version) Execute: ALTER EXTENSION pg_stat_monitor UPDATE; Observe the failure related to the histogram function/object conflict.