Itqualityassurance
- How many columns is too many in database?
- How many columns should a Postgres table have?
- Does number of columns affect performance in PostgreSQL?
How many columns is too many in database?
There is a hard limit of 4096 columns per table, but the effective maximum may be less for a given table. The exact limit depends on several interacting factors. Every table (regardless of storage engine) has a maximum row size of 65,535 bytes.
How many columns should a Postgres table have?
I ran into a situation today that was particularly frustrating, but for an interesting reason. PostgreSQL tables are hard-limited to a maximum of 1600 columns.
Does number of columns affect performance in PostgreSQL?
And the more I/O there is, the bigger the impact on performance. So yes, 250 columns typically means a bigger row size than for example 5 columns - and that reading a 1000 such rows of 250 cols each will require more I/O and thus have a bigger impact on performance, compared to reading a 1000 rows of 5 cols each.
