public inbox for pgsql-bugs@postgresql.org  

help / color / mirror / Atom feed

From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: siddharth.gupta@nutanix.com
Subject: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade
Date: Wed, 20 May 2026 09:23:35 +0000
Message-ID: <19489-c0714e0a647fbe05@postgresql.org> (raw)

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:        

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.

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, siddharth.gupta@nutanix.com
  Subject: Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade
  In-Reply-To: <19489-c0714e0a647fbe05@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox