Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: siddharth(dot)gupta(at)nutanix(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, PG Bug reporting form <noreply(at)postgresql(dot)org>
Subject: Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade
Date: 2026-05-21 20:51:19
Message-ID: 06592796-db3e-4b75-9da1-a28f25c22bf4@proxel.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 5/20/26 11:23 AM, PG Bug reporting form wrote:
> We observed a potential function name conflict between TimescaleDB and
> pg_stat_monitor during extension compatibility and upgrade validation.

Hi,

This does indeed seem quit unfortunate on our part but please report
this in our Github project rather than here. This mailing list is only
for bugs in PostgreSQL itself.

https://github.com/percona/pg_stat_monitor/issues

--
Andreas Karlsson
Percona

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Matheus Alcantara 2026-05-21 20:13:42 Re: BUG #19469: Prevent SIGSEGV on FETCH after ALTER TYPE of cursor rowtype