Every so often I need to find who exactly is damaging database performance. I mean – I have db connection which does something strange/wrong with the database, but what exactly is responsible?
Switching to separate user for every program, script and developer would solve the problem, but it is not always an option. So, what should I do?
Every now and then I see people ask the question – how to create table if it doesn't exist yet, how to drop it, but only if it does exist and so on.
Well, starting from 8.2 dropping should be not a problem anymore. But what about create? Alter?
Let's try to do it…
Yes, finally! David Fetter wrote, and Heikki Linnakangas committed patch which adds on/off arguments to \timing:
When I was working for one of customers we found some strange thing. We needed to found number of distinct sessions per day. Table layout was very simple:
I'm using .psqlrc file to set my preferable environment in psql. But I got lately annoyed by it confirming the changes every time I run psql:
Today we have two interesting patches:
Continue reading Waiting for 8.4 – partial-match support in GIN, and sequence restart
Another patch from Pavel Stehule – committed by Tom Lane. This patch adds CASE construction to pl/PgSQL:
Today another great patch, committed by Tom Lane. This patch was written by Martin Pihlak (with some edits by Tom).
Today we have one new feature – extension of plpgsql's RAISE command.
Friend from my previous employer told me that plans of execution of prepared statement, and the same statement run “as it" are different.
Well, I checked and this is what I found (it's not shocking, it's actually quite obvious, but You have to think about it for a while to “get it").