When messaging boards shift over to PostgreSQL, the "TOAST" capability seems likely to be a component that would have a highly material effect.
That is, columns that are large, such as text messages that may contain several kilobytes of data, will tend to get compressed and stored in a side table. There is initially some added cost to the compression, though on modern hardware, Dueling Cores, and such, there may be so much CPU power lying around that the cost won't be noticeable.
The benefits will be more noticeable - the large bits of data will get compressed, reducing the size of the database, and any queries that just hit the "metadata" will find that the metadata packs into pages way more compactly. (Rather than 2-3 tuples per page, it might increase to 20-30 tuples/page.)
TOAST benefits, maybe?
When messaging boards shift over to PostgreSQL, the "TOAST" capability seems likely to be a component that would have a highly material effect.
That is, columns that are large, such as text messages that may contain several kilobytes of data, will tend to get compressed and stored in a side table. There is initially some added cost to the compression, though on modern hardware, Dueling Cores, and such, there may be so much CPU power lying around that the cost won't be noticeable.
The benefits will be more noticeable - the large bits of data will get compressed, reducing the size of the database, and any queries that just hit the "metadata" will find that the metadata packs into pages way more compactly. (Rather than 2-3 tuples per page, it might increase to 20-30 tuples/page.)