Should I partition really big PostgreSQL tables?
January 28, 2011 4:48 AM Subscribe
Is it worth partitioning big (>1.5TB) tables in PostgreSQL? Most partitioning stuff seems to be based on the idea of sequential data, where older data is moved off onto secondary hardware or something, but this data is all equally important. I can't figure out if partitioning would be a win when all rows are equally likely to be accessed. If it makes a difference, most queries will access only one row, but multiple row queries will span multiple partitions regardless of the partitioning criteria I choose.