MIME-Version: 1.0
In-Reply-To: <19489-c0714e0a647fbe05@postgresql.org>
References: <19489-c0714e0a647fbe05@postgresql.org>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 20 May 2026 13:51:20 -0700
Message-ID: 
 <CAKFQuwbVS+rCj_oF-FdzhDRNFp=MkdFdE4cVPJBNUR9XH=kCGA@mail.gmail.com>
Subject: Re: BUG #19489: Function Name Conflict Between TimescaleDB and
 pg_stat_monitor Affecting Extension Upgrade
To: "siddharth.gupta@nutanix.com" <siddharth.gupta@nutanix.com>,
	"pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000050dc5a065245f561"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwbVS%2BrCj_oF-FdzhDRNFp%3DMkdFdE4cVPJBNUR9XH%3DkCGA%40mail.gmail.com>
Precedence: bulk

--00000000000050dc5a065245f561
Content-Type: text/plain; charset="UTF-8"

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.

--00000000000050dc5a065245f561
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, May 20, 2026, PG Bug reporting form &lt;<a href=3D"mailto:nor=
eply@postgresql.org">noreply@postgresql.org</a>&gt; wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">The following bug has been logged on the website:<br>
<br>
Bug reference:=C2=A0 =C2=A0 =C2=A0 19489<br>
Logged by:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Siddharth Gupta<br>
Email address:=C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:siddharth.gupta@nutani=
x.com">siddharth.gupta@nutanix.com</a><br>
PostgreSQL version: 18.4<br>
Operating system:=C2=A0 =C2=A0All<br>
Description:=C2=A0 =C2=A0 =C2=A0 =C2=A0 <br>
<br>
Hi Team,<br>
<br>
We observed a potential function name conflict between TimescaleDB and<br>
pg_stat_monitor during extension compatibility and upgrade validation.<br>
<br>
Details observed:<br>
<br>
PostgreSQL Version: All versions<br>
TimescaleDB Version: all versions<br>
pg_stat_monitor Version: All versions<br>
</blockquote><div><br></div><div>Neither of these projects is maintained by=
 the core project which is what this bug reporting mailing list is for.=C2=
=A0 You may wish to report this in a more appropriate location.=C2=A0 Thoug=
h usually the way to avoid this kind of problem is to install into separate=
 schemas.=C2=A0 If that is an option I hazard to say this is not a bug but =
simply not using the tools available to you.</div><div><br></div><div>David=
 J.</div><div>=C2=A0</div>

--00000000000050dc5a065245f561--