| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "siddharth(dot)gupta(at)nutanix(dot)com" <siddharth(dot)gupta(at)nutanix(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade |
| Date: | 2026-05-20 20:51:20 |
| Message-ID: | CAKFQuwbVS+rCj_oF-FdzhDRNFp=MkdFdE4cVPJBNUR9XH=kCGA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, May 20, 2026, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 19489
> Logged by: Siddharth Gupta
> Email address: siddharth(dot)gupta(at)nutanix(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2026-05-20 21:16:59 | BUG #19490: Streaming standby on 16.14 stops applying WAL on MultiXactOffsetSLRU when primary is 16.8 |
| Previous Message | Anton Fedorov | 2026-05-20 20:16:49 | Re: Fwd: Non-cancellable queries |