Skip to content

[Bug]: unqualified reference to current_database() in pg_extensions metric #10575

Description

@gbartolini

Is there an existing issue already for this bug?

  • I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

  • I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

  • I have read the troubleshooting guide and I think this is a new bug.

Contact Details

No response

Version

trunk (main)

What version of Kubernetes are you using?

1.35

What is your Kubernetes environment?

Self-managed: kind (evaluation)

How did you install the operator?

YAML manifest

What happened?

The pg_extensions metric in config/manager/default-monitoring.yaml is calling current_database() instead of pg_catalog.current_database()

Cluster resource

Relevant log output

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

  1. added this to the 1.29.1 milestone on Apr 29, 2026
  2. self-assigned this
    on Apr 29, 2026
  3. added a commit that references this issue on May 5, 2026
    675abf3
  4. added 2 commits that reference this issue on May 5, 2026
    0b522c3
    6a3a85b
  5. added 2 commits that reference this issue on May 5, 2026
    cad8929
    ac15301
  6. added a commit that references this issue on May 5, 2026
    f3a7926
  7. added
    bug 🐛Something isn't working
    and removed on Jun 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bug 🐛Something isn't workingtriagePending triage

Type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions