# Getting pg\_stat\_statements.blk\_read\_time error on Postgresql RDS 17

**URL:** <https://forums.percona.com/t/getting-pg-stat-statements-blk-read-time-error-on-postgresql-rds-17/39282>\
**Category:** PMM 2.x\
**Tags:** percona\
**Created:** [September 4, 2025, 12:44pm UTC](https://forums.percona.com/t/getting-pg-stat-statements-blk-read-time-error-on-postgresql-rds-17/39282 "2025-09-04T12:44:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Selva1](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/selva1/32/5510_2.png) [@Selva1](https://forums.percona.com/u/Selva1)\
**Post date:** [September 4, 2025, 12:44pm UTC](https://forums.percona.com/t/getting-pg-stat-statements-blk-read-time-error-on-postgresql-rds-17/39282/1 "2025-09-04T12:44:33Z")

</div>

## 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

##

---

<div class="post-metadata">

**Author:** ![amod\_kakade](https://avatars.discourse-cdn.com/v4/letter/a/65b543/32.png) [@amod\_kakade](https://forums.percona.com/u/amod_kakade)\
**Post date:** [September 23, 2025, 8:39am UTC](https://forums.percona.com/t/getting-pg-stat-statements-blk-read-time-error-on-postgresql-rds-17/39282/2 "2025-09-23T08:39:51Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Almaz\_Nazipov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/almaz_nazipov/32/20170_2.png) [@Almaz\_Nazipov](https://forums.percona.com/u/Almaz_Nazipov)\
**Post date:** [January 7, 2026, 11:33am UTC](https://forums.percona.com/t/getting-pg-stat-statements-blk-read-time-error-on-postgresql-rds-17/39282/3 "2026-01-07T11:33:27Z")

</div>

We had similar issue. I recreated the extension.

```sql
DROP EXTENSION pg_stat_statements;
CREATE EXTENSION pg_stat_statements;

```