>
> That is exactly what I want, and now I finally see how to do it (I
> think!). However, it is a considerable amount of work to set this up
> manually, plus, it has been a headache realizing how to get there at
> all. I'm hoping that one or more of the developers think it would be a
> good idea for PostgreSQL to perform an internal table optimization
> process using run-length encoding. Imagine you could just throw all your
> data into one table, run OPTIMIZE TABLE and you'd be done. With SQL
> being all about tables I'm surprised this idea (or something even
> better) hasn't been implemented already.
There was a recent brief thread here on storing timeseries data, where the
use of clustered indices for static tables was suggested. This might also
be useful in your situation...
Cheers,
Brent Wood
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
