Month: April 2014
The power of response times and execution time
The goal of the PostgreSQL optimizer is to provide you with a plan, which executes as fast as possible and returns all the data as rapidly as possible. In short: The game is about overall execution time of queries. However, there are cases in which you are not interested in receiving the entire result as […]
Regular expressions unleashed in PostgreSQL
When cleaning up some old paperwork this weekend I stumbled over a very old tutorial on regular expressions. In fact, I received this little handout during a UNIX course I attended voluntarily during my first year at university. It seems that those two days really changed my life – the price tag: 100 Austrian Shillings […]
Bypassing the transaction log
Referring to my previous blog post about the amount of xlog written by PostgreSQL I wanted to clarify what I meant when talking about bypassing the PostgreSQL transaction log. Normal WAL / xlog writes Whenever data is changed inside PostgreSQL the change must be written to the xlog before it is written to the underlying […]