public inbox for [email protected]help / color / mirror / Atom feed
BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade 3+ messages / 3 participants [nested] [flat]
* BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade @ 2026-05-20 09:23 PG Bug reporting form <[email protected]> 0 siblings, 2 replies; 3+ messages in thread From: PG Bug reporting form @ 2026-05-20 09:23 UTC (permalink / raw) To: [email protected]; +Cc: [email protected] The following bug has been logged on the website: Bug reference: 19489 Logged by: Siddharth Gupta Email address: [email protected] 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. ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade @ 2026-05-20 20:51 David G. Johnston <[email protected]> parent: PG Bug reporting form <[email protected]> 1 sibling, 0 replies; 3+ messages in thread From: David G. Johnston @ 2026-05-20 20:51 UTC (permalink / raw) To: [email protected] <[email protected]>; [email protected] <[email protected]> On Wednesday, May 20, 2026, PG Bug reporting form <[email protected]> wrote: > The following bug has been logged on the website: > > Bug reference: 19489 > Logged by: Siddharth Gupta > Email address: [email protected] > 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. ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade @ 2026-05-21 20:51 Andreas Karlsson <[email protected]> parent: PG Bug reporting form <[email protected]> 1 sibling, 0 replies; 3+ messages in thread From: Andreas Karlsson @ 2026-05-21 20:51 UTC (permalink / raw) To: [email protected]; [email protected]; PG Bug reporting form <[email protected]> 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2026-05-21 20:51 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-05-20 09:23 BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade PG Bug reporting form <[email protected]> 2026-05-20 20:51 ` David G. Johnston <[email protected]> 2026-05-21 20:51 ` Andreas Karlsson <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox