In this, hopefully 2nd to last, post in the series, I will cover the rest of usually happening operations that you can see in your explain outputs.

Word of warning: this blogpost is about thing related to Bash (well, maybe other shells too, didn't really test), but since I found it while doing Pg work, and it might bite someone else doing Pg related work, I decided ...

In previous post in the series I wrote about how to interpret single line in explain analyze output, it's structure, and later on described all basic data-getting operations (nodes in explain tree). Today, we'll move towards more complicated operations.

Last time I wrote about what explain output shows. Now I'd like to talk more about various types of "nodes" / operations that you might see in explain plans.

Around the time that Xzilla wrote about the book, Packt contacted me and asked for a review. Since I generally don't really read technical books, I declined the offer, but Sandy from Packt was very persistent, and asked if I could ...

One of the first things new DBA hears is "Use the EXPLAIN". And upon first try he/she is greeted with incomprehensible: ...

On 9th of April, Tom Lane committed patch: Support indexing of regular-expression searches in contrib/pg_trgm. This works by extracting trigrams from the given regular expression, in generally the same spirit as the previously-existing support for LIKE searches, though of course the details are far ...

On 4th of April, Tom Lane committed patch: Add \watch [SEC] command to psql. This allows convenient re-execution of commands. Will Leinweber, reviewed by Peter Eisentraut, Daniel Farina, and Tom Lane

Yesterday, I did release new version of OmniPITR - 1.1.0. You can get it from github or from PgXN. What's new? Couple of things:

So, I made some changes to explain.depesz.com, and while informing about it, I'd like to brag a bit about numbers, again :)