I recalled performing model verification for pgpool-II (a PostgreSQL replication tool) using SPIN in 2010, so I’m sharing some of the results.

In previous posts, post1 and post2, I demonstrated that it’s possible to continuously count the actual rows from EXPLAIN ANALYZE with an overhead of about 2.0%.

The next step is to examine methods for correcting the selectivity (or cardinality) estimation results.

Based on the improvements shown in this blog post, I will show the results of further optimizations.

In this blog, I’ll challenge conventional wisdom and explore methods to reduce overhead as much as possible. To that end, I will first discuss data types before explaining the specific improvements.

1-Line Abstract: Cut the overhead of EXPLAIN ANALYZE by roughly 77 [%].

I show a tip of autovacuum management.

As frequently mentioned, the table bloat problem is one of the most annoying things in managing PostgreSQL. Several things can cause that problem, and Autovacuum is one of them.

On March 8th, Datadog totally paralyzed around the world and it continued a few days.

I was interested in the caurses of that failure from the point of view of my pure engineering interest. However, Datadog have not disclosed anything yet.

I list up three kinds of technologies I am interested in except computing. If I were young, I would try to dive into these fields.

I’ve just released pg_plan_inspector that is a framework to monitor and improve the performance of PostgreSQL using Machine Learning methods.

One movie is worth a thousand words. Watch this movie.

I made a PostgreSQL’s module called shutdown_db using weekend time.

This module emulates the Oracle’s shutdown commands by controlling access for each DB.

pgindent maintains the uniform layout style of postgresql related source code.