Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Performance Insights not showing SQL Digest Statistics after PostgreSQL upgrade

1

I recently upgraded my RDS PostgreSQL instance from version 12.19 to 16.3. However, after the upgrade, Performance Insights displays the following message:

To enable SQL Digest Statistics for your version of PostgreSQL, please enable pg_stat_statements in your parameter group. Check the User Guide for more details.

The pg_stat_statements extension is already enabled in the parameter group, and its status is "in sync." I have also restarted the database instance, but the message persists.

Despite this, Performance Insights appears to be working normally.

Has anyone faced a similar issue? Is there anything else I need to check or configure?

Thanks!

Topics
AnalyticsMigration & ModernizationDatabase
Tags
Amazon Relational Database ServicePostgreSQLPerformance Insights
Language
English
asked a year ago541 views
2 Answers
0
Accepted Answer

Well, the issue was resolved along with the instability that was noted by AWS itself. I'm closing the thread here.

answered a year ago
0

This issue you're experiencing with Performance Insights not showing SQL Digest Statistics after upgrading your RDS PostgreSQL instance is not uncommon. Even though you've already enabled the pg_stat_statements extension and restarted the database instance, there are a few additional steps you can take to troubleshoot and potentially resolve this issue:

  1. Double-check that pg_stat_statements is properly loaded: Ensure that 'pg_stat_statements' is included in the 'shared_preload_libraries' parameter in your DB parameter group. If it's not there, add it and then reboot the DB instance.

  2. Verify the track_activity_query_size parameter: Performance Insights can only collect statistics for queries in pg_stat_activity that aren't truncated. By default, PostgreSQL truncates queries longer than 1,024 bytes. You may want to increase this limit by modifying the 'track_activity_query_size' parameter in your DB parameter group. Remember that changing this parameter requires a DB instance reboot.

  3. Disable and re-enable Performance Insights: Some users have reported success in resolving similar issues by disabling and then re-enabling Performance Insights at the cluster level. After doing this, it's recommended to reboot the instances to ensure the changes take effect.

  4. Check for any pending maintenance or updates: Ensure that there are no pending updates or maintenance tasks that might be interfering with the full functionality of Performance Insights after the upgrade.

  5. Verify compatibility: Confirm that all your current settings and extensions are fully compatible with PostgreSQL 16.3. The upgrade might have changed some default behaviors or requirements.

  6. Monitor and wait: Sometimes, it may take some time for all systems to sync up after a major version upgrade. Continue monitoring the situation, as the issue might resolve itself after a period of normal database activity.

If after trying these steps the issue persists, it would be advisable to contact AWS Support for further assistance, as they can provide more specific guidance based on your exact configuration and any potential known issues with the latest PostgreSQL version on RDS.

Remember, despite the message, you mentioned that Performance Insights appears to be working normally. This suggests that the issue might be more related to how the information is being displayed rather than a fundamental problem with data collection or functionality.

Sources
SQL statistics for RDS PostgreSQL - Amazon Relational Database Service
SQL statistics for Aurora PostgreSQL - Amazon Aurora
Performance Insights in RDS can't show the call/sec, Avg latency (ms)/call... | AWS re:Post

answered a year ago
EXPERT
reviewed a year ago
  • Wendel B
    a year ago

    Thanks for your detailed response. Here's an update based on your suggestions:

    pg_stat_statements is properly enabled and loaded in the shared_preload_libraries. track_activity_query_size is set to 4096, which should be sufficient for query collection. I’ve already tried disabling and re-enabling Performance Insights via AWS CLI, and I've restarted the RDS instance multiple times, but the issue persists. The instance has been live for several days, and there are no pending updates or maintenance tasks. Despite the warning message, Performance Insights appears to be working fine otherwise, as it continues to collect query performance data.

    As I’m on the AWS Basic Support Plan, the support options are limited.

    If anyone has faced a similar issue or has additional insights, I’d appreciate hearing about it.

  • Johannes
    a year ago

    We also noticed this problem and were just told by AWS support that this is an internal issue and they are working on a fix.

    You can actually see it in your Personal Health Dashboard:

    RDS operational issue [March 7 12:33 PM PST] We are continuing to investigate an issue with collecting SQL statistics in RDS Performance Insights for all RDS PostgreSQL instances, starting on February 18 at 5:01 PM PST. This has resulted in customers being unable to view, monitor, and troubleshoot critical query-level metrics, including Calls/sec, Rows/sec, and average latency. We were engaged on February 25 at 6:32 AM to investigate the issue, and have since identified the root cause. We have initiated a mitigation plan and are working to resolve the issue as quickly as possible. We will provide another update by March 11 at 12:00 PM or sooner if we have additional information.

  • Gary W
    a year ago

    We are also facing the same issue across all RDS PostgreSQL instances and have gotten no useful feedback from AWS Support for the past two weeks.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content