We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello, Issue trying Docker stack with image: pgpool/pgpool2_exporter@sha256:6748aff469abaa6f5aa150da7f70f1853eb9bf6250e78ab780fa5e8429f2f860
following error is logged:
2025-01-03T16:04:08.503595652Z [email protected] | ts=2025-01-03T16:04:08.503Z caller=pgpool2_exporter.go:715 level=info msg="error parsing" err="Unexpected error parsing column: pool_nodes replication_delay [48 46 48 48 48 53 54 56 32 115 101 99 111 110 100]\n"
Pgpool is v4.5.5. Output from 'show pool_nodes;':
-[ RECORD 1 ]----------+-------------------- node_id | 0 hostname | db1 port | 5445 status | up pg_status | up lb_weight | 0.142857 role | primary pg_role | primary select_cnt | 429328 load_balance_node | false replication_delay | 0 replication_state | replication_sync_state | last_status_change | 2025-01-01 01:22:03 -[ RECORD 2 ]----------+-------------------- node_id | 1 hostname | db2 port | 5445 status | up pg_status | up lb_weight | 0.857143 role | standby pg_role | standby select_cnt | 3196857 load_balance_node | true replication_delay | 0.000631 second replication_state | streaming replication_sync_state | async last_status_change | 2025-01-01 01:22:03
Am I missing something in pgpool or Postgres configuration?
Thanks.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
Issue trying Docker stack with image:
pgpool/pgpool2_exporter@sha256:6748aff469abaa6f5aa150da7f70f1853eb9bf6250e78ab780fa5e8429f2f860
following error is logged:
Pgpool is v4.5.5.
Output from 'show pool_nodes;':
Am I missing something in pgpool or Postgres configuration?
Thanks.
The text was updated successfully, but these errors were encountered: