(Keith) When I say version specific here, I’m speaking of the PostgreSQL version (9.1, 9,2, etc), not the extension version. An upcoming update to PG Partition Manager takes advantage of the range data type, which is a 9.2 feature. But I also wanted to keep backward compatibility with 9.1 by excludi

(Ovais Tariq) The other day I was working on an issue where one of the slaves was showing unexpected lag. Interestingly with only the IO thread running the slave was doing significantly more IO as compared to the rate at which the IO thread was fetching the binary log events from the master.

(Michael Paquier) When scanning a relation with a query with a bitmap heap scan and that the bitmap is not large enough to contain a reference to each tuple individually, bitmap heap scan switches to lossy mode where instead of the tuples relation pages are referenced in the bitmap.

(Morgan Tocker) MySQL has sometimes faced criticism for being too relaxed at allowing invalid values, or inserting but truncating values that are out of range. For example:

(Rob Gravelle) There are a lot of occasions for converting one data type to another. Examples include porting data from one database vendor to another, changing the data type of a column, and temporarily switching between data types for evaluation.

(depesz) On 23rd of December, Tom Lane committed patch:

(Manku) This is the very first post in the series of Performance Schema Implementation Internals. This series is for MySQL Developers to understand implementation of Performance Schema.

(Keith Fiske) One of the biggest advantages of table partitioning in databases is taking advantage of a feature called constraint exclusion. The PostgreSQL docs explain this best:

(Anders Karlsson) The Open Source movement is full of myths, there are different myths from inside the movement (i.e. those who live and breath Open Source or at least thinks it’s a good thing) and outside (i.e. those who do not think Open Source really is a good idea to those who thinks Open Source

(Alexander Rubin) MySQL and Scaling-up (using more powerful hardware) was always a hot topic. Originally MySQL did not scale well with multiple CPUs; there were times when InnoDB performed poorer with more CPU cores than with less CPU cores. MySQL 5.6 can scale significantly better; however there i