> Probably by carefully partitioning their data. I can't imagine anything
> being fast on a single table in 250,000,000 tuple range. Nor can I
> really imagine any database that efficiently splits a single table
> across multiple machines (or even inefficiently unless some internal
> partitioning is being done).
Ah, what about partial indexes - those might help. As a kind of
'semi-partition'.
Chris
