Getting pg_stat_statements.blk_read_time error on Postgresql RDS 17

Percona Monitoring and Management (PMM) PMM 2.x
1

Description:

Setting up Percona monitoring for AWS RDS PostgreSQL 17.5

Steps to Reproduce:

Launch AWS RDS PostgreSQL 17.5 and Perform Percona Monitoring with PMM 2.41.2

Version:

AWS RDS PostgreSQL 17.5

Percona Monitoring 2.41.2

Logs:

time=“2025-09-04T11:38:23.724+00:00” level=info msg=“Sending status: STARTING.” agentID=/agent_id/c38ae580-6094-421c-9c9a-b66b7ec20b8f component=agent-builtin type=qan_postgresql_pgstatements_agent
time=“2025-09-04T11:39:00.003+00:00” level=info msg=“Sending status: STARTING.” agentID=/agent_id/c38ae580-6094-421c-9c9a-b66b7ec20b8f component=agent-builtin type=qan_postgresql_pgstatements_agent
time=“2025-09-04T11:39:00.064+00:00” level=error msg=“couldn’t get rows from pg_stat_statements: pq: column pg_stat_statements.blk_read_time does not exist” agentID=/agent_id/c38ae580-6094-421c-9c9a-b66b7ec20b8f component=agent-builtin type=qan_postgresql_pgstatements_agent
time=“2025-09-04T11:39:00.064+00:00” level=info msg=“Sending status: WAITING.” agentID=/agent_id/c38ae580-6094-421c-9c9a-b66b7ec20b8f component=agent-builtin type=qan_postgresql_pgstatements_agent

Expected Result:

We should monitor pg_stat_statements records but its keep saying waiting

Actual Result:

Query Analytics capture complete

2

I am seeing exact same issue even onprem, linux build.

The pmm-agent prints following mesage on journalctl

=“pq: column \“checkpoints_timed\” does not exist”"
pq: column pg_stat_statements.blk_read_time does not exist