pgexporter_ext
Overview
| Package | Version | Category | License | Language |
|---|---|---|---|---|
pgexporter_ext | 0.2.5 | STAT | BSD-3-Clause | C |
| ID | Extension | Bin | Lib | Load | Create | Trust | Reloc | Schema |
|---|---|---|---|---|---|---|---|---|
| 6430 | pgexporter_ext | No | Yes | No | Yes | No | Yes | - |
Release/control and PIGSTY DEB version are 0.2.5; principal PGDG RPM is 0.2.4, except EL8 PG14-16 at 0.2.3. The guide configures preload, but 0.2.5 metrics work without it (verified). Metric access requires pg_monitor; local build capability does not authorize replacing PGDG packages.
Version
| Type | Repo | Version | PG Ver | Package | Deps |
|---|---|---|---|---|---|
| EXT | PGDG | 0.2.5 | 1817161514 | pgexporter_ext | - |
| RPM | PGDG | 0.2.4 | 1817161514 | pgexporter_ext_$v | - |
| DEB | PIGSTY | 0.2.5 | 1817161514 | postgresql-$v-pgexporter-ext | - |
Build
You can build the RPM / DEB packages for pgexporter_ext using pig build:
Install
You can install pgexporter_ext directly. First, make sure the PGDG and PIGSTY repositories are added and enabled:
Install the extension using pig or apt/yum/dnf:
Create Extension:
Usage
Sources:
- Version 0.2.5 README
- Version 0.2.5 setup guide
- Version 0.2.5 SQL definitions
- Version 0.2.3 SQL definitions
- Version 0.2.4 SQL definitions
- Version 0.2.5 filesystem implementation
pgexporter_ext exposes Linux host and filesystem metrics through SQL for collection by pgexporter. The examples below apply to the packaged 0.2.3–0.2.5 APIs. Functions run with the PostgreSQL operating-system account’s access, so restrict the monitoring role to trusted users.
Setup and Core Workflow
The upstream setup guide configures the module in shared_preload_libraries, followed by a PostgreSQL restart. Preserve any other libraries already configured.
In the postgres database, a privileged administrator installs the extension and grants monitoring access to the existing exporter login:
The SQL scripts revoke public execution and grant it to pg_monitor. That predefined role also grants broad PostgreSQL monitoring access. The release includes a base installation script and an upgrade chain; PostgreSQL can use that chain when installing the default version with CREATE EXTENSION.
Metric Functions
pgexporter_information_ext()andpgexporter_version_ext()return extension information and version text.pgexporter_get_functions()lists metric names, whether they take input, descriptions, and types.pgexporter_is_supported(text)checks a metric name.pgexporter_os_info(),pgexporter_cpu_info(),pgexporter_memory_info(),pgexporter_network_info(), andpgexporter_load_avg()return host metrics.pgexporter_used_space(text),pgexporter_free_space(text), andpgexporter_total_space(text)return byte counts for a filesystem path.
Choose a path that exists on the server and is accessible to its operating-system account. These releases do not provide the later FIPS or log-count APIs.
Operational Boundaries
Filesystem calls use the server’s filesystem view, which may be a container rather than the host. The used-space function walks directories, so large trees can make scrapes expensive. A pg_monitor member can inspect accessible paths; restrict database access and choose collection paths deliberately.
Upstream lists Linux and PostgreSQL 13+; this catalog supplies packages for PostgreSQL 14–18. Use the exact PostgreSQL-major package. The principal RPM supplier is PGDG at 0.2.4 (EL8 PostgreSQL 14–16 use 0.2.3), while Pigsty supplies DEB 0.2.5; enable the Pigsty repository as well when following the cross-platform installation instructions.
Was this page helpful?
Thanks—your feedback helps us improve this page.
What got in the way? (optional)