> > Also, how are people handling tables with lots of rows? The 8k tuple
> > size can waste a lot of space. I need to be able to handle a 2 million
> > row table, which will eat up 16GB, plus more for indexes.
>
> This oen is improved upon in v6.3, where at compile time you can stipulate
> the tuple size. We are looking into making this an 'initdb' option instead,
> so that you can have the same binary for multiple "servers", but any database
> created under a particular server will be constrained by that tuple size.
Tom's "problem" is probably not a bad as he thinks. The 8k tuple size limit is a
result of the current 8k page size limit, but multiple tuples are allowed on a page.
They are just not allowed to span pages. So, there is some wasted space (as is true
for many, most, or all commercial dbs also) but it is on average only the size of
half a tuple, and can be easily predicted once the tuple sizes are known.
- Tom (T2?)