Postgres Performance: Static row length?

Mysql behaves in a special (presumably more performant) manne开发者_Python百科r when a table has no variable-width columns

Does postgres have similar behavior? Does adding a single variable-width column to a table make any major difference?

---

The general advice given in the postgres docs (read the tip) is that variable length fields often perform better because it results in less data so the table fits in less disk blocks and takes up less space in cache memory. Modern CPU's are so much faster then the memory and disks that the overhead of variable length field is worth the reduction in IO.

Notice that postgresql stores NULL values in a bitmap at the beginning of the row and omits the field if the value is NULL. So any nullable column has basically a variable width. The way postgresql stores it data (Database page layout) suggests that retrieving the last column would be slower then the first column. But this will probably only have a noticable impact if you have many columns and the data was mostly in cache to start with. Otherwise the disk io will be the dominant factor.

---

From what I know, no it doesn't

Check this link out for general talk about datatypes my conclusion from this read is whatever special behavior mysql exhibits, postgresql doesn't which to me is good. http://www.depesz.com/index.php/2010/03/02/charx-vs-varcharx-vs-varchar-vs-text/

---

presumably more performant

I would never ever believe any "performance myth" unless I test it with my own set of data and with a workload that is typical for my application.

If you need to know if your workload is fast enough on DBMS X with your data, don't look at anything else than the numbers you obtain from a realistic benchmark in your environment with hardware that matches production.

Any other approach can be replaced by staring at good crystal ball