QAN does not show the PostgreSQL queries with Full Table scan

Hi Team,

We just did a few load tests on the PostgresDB server. During the load test, the CPU utilization went up to 99%. For example, following the load test, we conducted our own analysis and discovered a few queries that do a full table scan but are not shown in the QAN.

Could you please assist us in identifying the queries which are doing the full table scan?

@Roma_Novikov @nurlan Can you please help me on this?

Hello @Naresh9999, sorry currently I’m a bit busy and can’t assist with this problem. Could you please add more details on how did you perform load test and share how did you compare results.

@nurlan Can you please guide me on where I can check or which columns we can consider for a PostgreSQL table full scan?

Can you please help me with the columns that we check for the table full scan using pmm.metrics table?

Hi, we don’t collect information about fullscan for PostgreSQL as this information doesn’t exist in pg_stat_statements.

@nurlan Actually my query source is pg_stat_monitor and postgresql version 16.

Pmm version: 3.1.0

We don’t collect full scan from pgsm as well

Okay @nurlan got it.

Thanks for the update.