public inbox for pgsql-bugs@postgresql.org  

help / color / mirror / Atom feed

From: David G. Johnston <david.g.johnston@gmail.com>
To: siddharth.gupta@nutanix.com <siddharth.gupta@nutanix.com>
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade
Date: Wed, 20 May 2026 13:51:20 -0700
Message-ID: <CAKFQuwbVS+rCj_oF-FdzhDRNFp=MkdFdE4cVPJBNUR9XH=kCGA@mail.gmail.com> (raw)
In-Reply-To: <19489-c0714e0a647fbe05@postgresql.org>
References: <19489-c0714e0a647fbe05@postgresql.org>

On Wednesday, May 20, 2026, PG Bug reporting form <noreply@postgresql.org>
wrote:

> 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
>

Neither of these projects is maintained by the core project which is what
this bug reporting mailing list is for.  You may wish to report this in a
more appropriate location.  Though usually the way to avoid this kind of
problem is to install into separate schemas.  If that is an option I hazard
to say this is not a bug but simply not using the tools available to you.

David J.

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: david.g.johnston@gmail.com, siddharth.gupta@nutanix.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade
  In-Reply-To: <CAKFQuwbVS+rCj_oF-FdzhDRNFp=MkdFdE4cVPJBNUR9XH=kCGA@mail.gmail.com>

* 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