PgBadger is a PostgreSQL log analyzer with fully detailed reports and graphs. It is open source and is considered lightweight. While it doesn’t have the depth, probe capability or tool integration that EDB Postgres Enterprise Manager does, it’s particularly useful in helping you to analyze your slowest queries, and also does a good job of profiling Temporary Files, Connection Peak, Autovacuum/Autoanalyze, Checkpoints, etc which can help in demonstrating overall health of the database.

In this session, our Postgres experts discuss PgBadger and how it can help with Postgres query performance.

Learn more about this topic in this blog post: https://www.enterprisedb.com/blog/how-to-use-pgbadger-log-analyzer-postgresql-query-performance, and follow all of our updates here: https://www.enterprisedb.com/postgres-pulse.

A corruption in the database base often manifests itself in the form of errors when performing a DDL or DML operation on affected relations. The errors often show up as errors reading tables due to a missing file—that is rather straightforward, of course. However, a corrupt index is not as obvious as a corrupt table. More often than not to find if indeed there is index corruption, one needs to observe the behavior (execution times) and results of the queries themselves.

In this episode, we dive into questions and quagmires around index corruption and related issues.

For more information on this topic, visit this blog: https://www.enterprisedb.com/blog/how-to-fix-postgresql-index-corruption-deal-repair-rebuild, and follow all of our updates here: https://www.enterprisedb.com/postgres-pulse.

When it comes to dealing with poor database and query performance, it’s a daunting task to venture into the dark cavern of query planning and optimization, but fear not! EXPLAIN is our friend in those dark and lonely places.

This episode covers EXPLAIN and how it is certainly one of the most invaluable tools for anyone working with PostgreSQL. Using it well will save you lots of time!

For more information on this topic, visit this blog: https://www.enterprisedb.com/postgresql-query-optimization-performance-tuning-with-explain-analyze, and follow all of our updates here: https://www.enterprisedb.com/postgres-pulse.

Planning is key to PostgreSQL backup and recovery. Every environment has its own challenge—and even if we have multiple database clusters in the same organizations, the backup requirements for those might also vary. Therefore, it is important to list down the situations we might need to recover from and then discuss the possible solutions available.

In this episode, we discuss PostgreSQL backup woes, successes, and strategies.

To learn more about this topic, visit this blog: https://www.enterprisedb.com/blog/postgresql-database-backup-recovery-what-works-wal-pitr, and follow all of our updates here: https://www.enterprisedb.com/postgres-pulse.

With the ongoing crisis of COVID-19, I keep myself updated with the latest situation around the globe. The WHO’s website is one I’ve used frequently—and even there I began to intermittently see the error message “sorry, too many clients already“ in my browser. In seeing this, I realized how common it is to underestimate the connection count while we are busy configuring the application.

The above is a scenario we may all face today in our daily lives where a connection load problem may arise, and there are many things you can infer from the message. This episode aims to help you understand how this can be handled in a planned manner with the help of PgPool. For more information, visit: https://www.enterprisedb.com/blog/postgresql-pgpool-connection-pool-database-load, and follow all of our updates here: https://www.enterprisedb.com/postgres-pulse.

Most DBAs have run into issues where users can't access the database and alert that the database may be down. In this case, when DBAs dive into the issue, they find out that the database is up - just not for everyone.

One common cause of these problems is an authentication error. In this episode, we dive into PostgreSQL LDAP authentication problems and how to fix them. For more details, take a look at this blog post: https://www.enterprisedb.com/blog/i-cant-get-database-it-down-postgresql-ldap-authentication-problems, and follow all of our updates here: https://www.enterprisedb.com/postgres-pulse.

Identifying exactly what causes a slow Postgres database and then optimizing PostgreSQL performance is the most important task for DBAs.

One of the most widespread issues we see hit almost every database from time to time is poor performance. Database administrators are often bombarded by end-users with complaints about the database being slow. You’re expected to act quickly in order to diagnose and fix the problem.

In this episode, our Postgres experts dive into this issue and provide key tactics for successfully approaching this problem.

For more information, take a look at this blog: https://www.enterprisedb.com/blog/postgres-pulse-insights-its-still-slow-solving-bloated-postgres-database, and follow all of our updates here: https://www.enterprisedb.com/postgres-pulse.

We get numerous tech issues and common database symptoms flagged to our team on a daily basis. And given the current landscape fraught with uncertainty, these, along with many new and pressing questions, are filing in at greater volumes. Now is the right time to use what we know to help you in your Postgres experience.

Introducing: Postgres Pulse, a weekly blog and video forum series built to offer insight into how we analyze problems and develop solutions using Postgres. Our Postgres Pulse Insights blogs and Postgres Pulse podcast episodes focus on trending questions, common challenges, and how to solve the top issues you may face in your Postgres environment.

For more details, take a look at our blog on this topic: https://www.enterprisedb.com/blog/introducing-postgres-pulse-insights-live-qa-postgres-experts, and follow all of our updates here: https://www.enterprisedb.com/postgres-pulse.