> > > 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.
> 16GB?!? Not unless your tuples are 8k. The 8k is/was the max _tuple_ size,
> but more than one tuple can be stored per block. :)
> Try the formula in the FAQ to get a reasonable estimate for the table's size.
The FAQ copy on the web page has it. The FAQ in the 6.2.1 distribution
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 1998-01-18 02:59:43|
|Subject: Re: [HACKERS] S_LOCK() change produces error...|
|Previous:||From: The Hermit Hacker||Date: 1998-01-18 02:35:52|
|Subject: More on free() bug...|