pganalyze for PostgreSQL
pganalyzeReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
34 reviews
from
External reviews are not included in the AWS star rating for the product.
Perfect solution to monitor PostgreSQL status even for developpers
What do you like best about the product?
The product goes to the right direction. It's full of great views about indexes, current running queries, performances. Auto-explain view is perfect to understand why a query was slow. Team is super reactive on feature request or misunderstanding. It's great to have technical people that answer you. We use it daily and we do not have dba. It's used by developers and more experienced PostgreSQL users.
What do you dislike about the product?
Because it is used by all type of database, it's sometimes not the perfect tool for I/O bound DB from AWS. Sometime we need to look at Performance Insight on AWS then switch back on PgAnalyze to get more details and continue our investigation.
What problems is the product solving and how is that benefiting you?
It help me understanding the status of the db, and why we can have slower queries or wrong PostgreSQL settings.
PGANALYZE REVIEW
What do you like best about the product?
The aboility to analyze data with postgres
What do you dislike about the product?
I have nothing to dislike except it is not a well known tool
What problems is the product solving and how is that benefiting you?
it is solving issues related to monitoring databases
Good Tool for analysing DB Query and performance
What do you like best about the product?
I believe its most appealing aspect is its ability to provide actionable insights into PostgreSQL query performance. By analyzing query plans, identifying slow queries, and suggesting optimizations, pganalyze empowers database administrators to proactively tune their systems and ensure optimal performance.
What do you dislike about the product?
Performance Optimization: By identifying slow queries and suggesting optimizations, pganalyzer helps database administrators improve overall system efficiency.
Proactive Monitoring: pganalyzer can be used to continuously monitor database performance and detect potential issues before they impact operations.
Complexity: pganalyzer's features and analysis can be complex for users who are not familiar with PostgreSQL internals and performance optimization techniques.
Resource Requirements: Running pganalyzer may require additional system resources, especially for large or heavily loaded databases.
Proactive Monitoring: pganalyzer can be used to continuously monitor database performance and detect potential issues before they impact operations.
Complexity: pganalyzer's features and analysis can be complex for users who are not familiar with PostgreSQL internals and performance optimization techniques.
Resource Requirements: Running pganalyzer may require additional system resources, especially for large or heavily loaded databases.
What problems is the product solving and how is that benefiting you?
To monitoring db operation and summarized queries.
Awesome tool for PostgreSQL performance monitoring
What do you like best about the product?
It is very easy to find out the slow running queries ,they can be tuned and performance increases
Allows us to see the CPU ,I/O metrics and check any abnormality through the mails received to us.
Weekly performance and health of the server reports are generated
Allows us to see the CPU ,I/O metrics and check any abnormality through the mails received to us.
Weekly performance and health of the server reports are generated
What do you dislike about the product?
Nothing much could be said as disadvantage as of now.It is more advanced than pgbadger
What problems is the product solving and how is that benefiting you?
There are multiple PostgreSQL servers in different environments as dev,test,pre prod,prod and all the servers could be easily maintained and checked for alerts
Any performance tuning suggestions also given by pganalyze like index utilization for a table or vaccuum when was it done last
Any performance tuning suggestions also given by pganalyze like index utilization for a table or vaccuum when was it done last
showing 31 - 34