We have a production database with transaction-style data, in most of the tables we have a timestamp attribute "created" telling the creation time of the table row. Naturally, this attribute is always increasing.
By now we are hitting the limit where the table data does not fit in caches anymore. We have a report section where there are constantly requests for things like "sum up all transactions for the last two weeks", and those requests seem to do a full table scan, even though only the last parts of the table is needed - so by now those reports have started to cause lots of iowait. Is there any way to avoid this, apart from adding memory linearly with database growth, make adjunct tables for historical rows, or build a separate data warehousing system? There must be some simpler solutions, right? -- Tobias Brox, Beijing ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])