Postgres Connection Tracing, Wait Event Analysis & Vacuum Monitoring go into GA on pganalyze
14 April, 2019We’re excited to announce the general availability of three new pganalyze features: Connection Tracing , Wait Event Analysis , as well as Vacuum Monitoring . These features have been developed based on the feedback of hundreds of customers monitoring their production Postgres databases using pganalyze. Thanks so much for consistently taking the time to provide us with valuable information on how you’d like to see pganalyze evolve! Postgres Connection Tracing & Wait Event Analysis One of the…
Continue readingNew in Postgres 11: Monitoring JIT performance, Auto Prewarm & Stored Procedures
04 October, 2018Everyone’s favorite database, PostgreSQL, has a new release coming out soon: Postgres 11 In this post we take a look at some of the new features that are part of the release, and in particular review the things you may need to monitor, or can utilize to increase your application and query performance. Just-In-Time compilation (JIT) in Postgres 11 Just-In-Time compilation (JIT) for query execution was added in Postgres 11. It's not going to be enabled for queries by default, similar to parallel…
Continue readingPostgres Log Monitoring with pganalyze: Introducing Log Insights 2.0
24 July, 2018TLDR: We recently released substantial improvements to our Log Insights feature, including up to 30 day history, support for Heroku Postgres, as well as support for monitoring the log files of PostgreSQL servers running on-premise. How pganalyze parses Postgres log files Its now been a bit over a year since we first released the log monitoring functionality in pganalyze, and we would like to share a major update with you today. Before diving in, a quick review how the pganalyze collector…
Continue readingPostgres Log Monitoring 101: Deadlocks, Checkpoint Tuning & Blocked Queries
12 February, 2018Those of us who operate production PostgreSQL databases have many jobs to do - and often there isn't enough time to take a regular look at the Postgres log files. However, often times those logs contain critical details on how new application code is affecting the database due to locking issues, or how certain configuration parameters cause the database to produce I/O spikes. This post highlights three common performance problems you can find by looking at, and automatically filtering your…
Continue readingVisualizing & Tuning Postgres Autovacuum
28 November, 2017In this post we'll take a deep dive into one of the mysteries of PostgreSQL: VACUUM and autovacuum. The Postgres autovacuum logic can be tricky to understand and tune - it has many moving parts, and is hard to understand, in particular for application developers who don't spend all day looking at database documentation. But luckily there are recent improvements in Postgres, in particular the addition of pg _ stat _ progress _ vacuum in Postgres 9.6, that make understanding autovacuum and…
Continue readingWhats New in Postgres 10: Monitoring Improvements
04 October, 2017Postgres 10 has been stamped on Monday, and will most likely be released this week, so this seems like a good time to review what this new release brings in terms of Monitoring functionality built into the database. In this post you'll see a few things that we find exciting about the new release, as well as some tips on what to adjust, whether you use a hosted Postgres monitoring tool like pganalyze, or if you've written your own scripts. New "pg_monitor" Monitoring Role Most users of Postgres…
Continue readingIntroducing Log Insights: Realtime Analysis of Postgres Logs
07 June, 2017After significant development effort, we're excited to introduce you to a new part of pganalyze that we believe every production Postgres database needs: pganalyze Log Insights UPDATE: We released pganalyze Log Insights 2.0 - read more about it in our article: Postgres Log Monitoring with pganalyze: Introducing Log Insights . In the past you used generic log management systems and setup your own filtering and altering rules, which required a lot of manual effort, as well as knowledge of all…
Continue readingMonitoring PostgreSQL 9.5 & Improved Weekly Reports
06 July, 2015Last week the first official alpha version of PostgreSQL 9.5 was released . Whilst the stable release is still 2-3 months away, now is a good time to review what is upcoming, and which changes and improvements we can expect. Here is an overview of the most important changes for monitoring tools: pg _ stat _ statements gets new columns min _ time, max _ time, mean _ time & stddev _ time - making it much easier to identify outliers in the query statistics New pg _ stat _ ssl view that shows…
Continue readingIntroducing pg_query: Parse PostgreSQL queries in Ruby
17 June, 2014In this article we'll take a look at the new pg_query Ruby library. pg_query is a Ruby library I wrote to help you parse SQL queries and work with the PostgreSQL parse tree. We use this extension inside pganalyze to provide contextual information for each query and find columns which might need an index. At the end of this article you'll also find monitor.rb - a ready-to-use example that filters pg _ stat _ statements output and restricts it to only show a specific table. Existing…
Continue readingAnnouncing The All-New Database Check-Up
20 March, 2014We’ve just launched our new version of Database Check-Up - allowing you to see more quickly what could be relevant to look at in your database. In addition we’ve also revamped the detail pages of queries, tables, indices and config settings to match the new style: Improved Check-Up: Config Settings When working with other people's PostgreSQL databases, we’ve seen a lot of things, from fsync=off (which you really only want if you don’t care about your data or have no writes) to simple…
Continue reading