Inspired by some previous posts on PostgreSQL security barriers I had the idea of abusing PostgreSQL security barriers (http://www.postgresql.org/docs/9.3/static/sql-createview.html) to cheat on the optimizer. I have constructed an example how a security barrier can theoretically be used to speed up things under some very nasty circumstances. (more…)
Christmas is approaching fast so I thought I’d give PostgreSQL users some inspiration when it comes to buying their Christmas presents. I assume that I am not the only one who has constant troubles finding the right present for somebody. The trouble is that prices are usually strange numbers. Maybe EUR 49.95 or EUR 49.99. This makes it very hard to look for something that costs, say, EUR 50. (more…)
PostgreSQL knows a parameter called effective_cache_size. To many this is one of the most mysterious settings in the entire PostgreSQL config. Maybe this is the core reason why many people just completely ignore this setting – in many cases this is not the best idea of all. effective_cache_size can have a serious impact on execution plans and change things dramatically. So, it is definitely a good idea to take this into account and see, which difference it can make. (more…)
After my morning session in Dublin some people asked me to share the codes of an operator class I have created for demo reasons. This posting is supposed to cover those codes.
What is an operator class?
In PostgreSQL an index is not a hardwired thing, capable of following just one strategy. Instead an index is more of a framework people can use to implement their own indexing strategies. What is the point of all that? (more…)
PostgreSQL has a sophisticated security system capable of handling complex policies and user permissions are an essential component of every productive setup many people rely on. However, over the past couple of years I have noticed that many users fall into the same trap: The “public” schema. (more…)