Thanks for all your responses and my apologies for putting the question in
the wrong list.
I think OLAP is the answer for my requirements.
Regards,
Hardik
On Wed, Aug 4, 2010 at 5:40 AM, Greg Smith wrote:
> Hardik Belani wrote:
>
>> For this i can create a table with number and time (may be
Hardik Belani wrote:
For this i can create a table with number and time (may be time offset
instead of timestamp) as columns. But still it will require me to
store huge number of rows in the order of few millions. Data is read
only and only inserts can happen. But I need to perform all kinds of
On 02/08/2010 3:20 AM, Hardik Belani wrote:
We are using postgres as RDBMS for our product. There is a requirement
coming for a feature which will require me to store data about various
data points (mainly numbers) on a time scale. Data measurement is
being taken every few secs/mins based and i
On Mon, Aug 2, 2010 at 3:20 AM, Hardik Belani wrote:
> We are using postgres as RDBMS for our product. There is a requirement
> coming for a feature which will require me to store data about various data
> points (mainly numbers) on a time scale. Data measurement is being taken
> every few secs/mi
We are using postgres as RDBMS for our product. There is a requirement
coming for a feature which will require me to store data about various data
points (mainly numbers) on a time scale. Data measurement is being taken
every few secs/mins based and it is needed to be stored for statistical
analysi