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

Analyze your Amazon RDS and Aurora PostgreSQL workloads

Language: English
Analyze your Amazon RDS and Aurora PostgreSQL workloads
0
Do you want to better understand your Amazon RDS and Aurora PostgreSQL workloads? Explore these curated resources for the best practices to analyze your Amazon RDS and Aurora PostgreSQL workloads.
Topics
AnalyticsMigration & ModernizationDatabase
Tags
Aurora PostgreSQLAmazon Relational Database Service
AWS OFFICIALUpdated 3 years ago147 views

Performance Insights

It's a best practice to use the Performance Insights dashboard to analyze your Amazon RDS metrics, DB load, database performance, and top SQL queries.

Using Performance Insights to Analyze Performance of Amazon Aurora PostgreSQL

Watch this video for a demonstration of using Amazon RDS Performance Insights to analyze performance of an Amazon Aurora PostgreSQL database instance.

Overview of the Performance Insights dashboard

Review this AWS Documentation for an overview of the Performance Insights dashboard.

Performance Insights Top SQL console

The dashboard displays top SQL queries that are contributing to the database load. The console also shows relevant statistics for each statement.

Identify top and slow queries

It's a best practice to identify top and slow queries and analyze Amazon RDS for PostgreSQL logs in Amazon Cloudwatch.

PostgreSQL documentation for pg_stat_statements view

This Aurora PostgreSQL documentation describes the module statistics that help with tracking and planning. To use this view, you must set the value of shared_preload_libraries to pg_stat_statements.

How can I resolve the "ERROR: ˂module/extension˃ must be loaded via shared_preload_libraries" error

This article explains the prerequisite of how to set the value of shared_preload_libraries to pg_stat_statements in a custom parameter group that's associated with your DB instance.

How do I turn on query logging using Amazon RDS for PostgreSQL?

Watch this video to learn how to turn on query logging for Amazon RDS for PostgreSQL.

Publishing PostgreSQL logs to Amazon CloudWatch Logs

Learn how to publish your PostgreSQL log files to CloudWatch Logs for further analysis.

Troubleshoot performance issues in RDS and Aurora PostgresQL

This article covers how to identify and troubleshoot performance issues and slow-running queries in my RDS for PostgreSQL or Aurora PostgreSQL instances.

Handle idle and idle in transactions

It's a best practice to check the status of your DB connections, and then stop idle sessions to keep your database running smoothly.

PostgreSQL documentation for pg_stat_activity view

This Aurora PostgreSQL documentation describes the pg_stat_activity view. Use this view to check the status of the connection of your Aurora PostgreSQL instance.

PostgreSQL documentation for idle_in_transaction_session_timeout (integer)

Use this parameter to stop sessions with an open transaction that has been idle for longer than the specified duration in milliseconds.

Collect and monitor statistics

It's a best practice to collect and monitor various statistic functions of your Aurora PostgreSQL workloads for performance.

PostgreSQL documentation for statistics collector

This PostgreSQL documentation explains PostgreSQL's statistics collector subsystem. Use the statistics collector to collect and report information about your server activity.

PostgreSQL documentation for cumulative statistics system

This PostgreSQL documentation covers the cumulative statistics system. Use this system to collect and report your server activity.

Additional statistics functions

This PostgreSQL documentation describes various statistic functions that you can use to monitor your DB.

Statistics used by the planner

This PostgreSQL documentation describes the statistics that the query planner uses for estimates.

Cumulative query and index statistics

Configure these parameters to fine tune the collection of statistics you want to capture and reduce overhead for running queries.
No comments

Relevant content