Re: Using Postgres to store high volume streams of sensor readings - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Using Postgres to store high volume streams of sensor readings
Date
Msg-id dcc563d10811221709s38d4e65ex8c821ef65491cf5e@mail.gmail.com
Whole thread Raw
In response to Re: Using Postgres to store high volume streams of sensor readings  (Scara Maccai <m_lists@yahoo.it>)
Responses Re: Using Postgres to store high volume streams of sensor readings
List pgsql-general
On Sat, Nov 22, 2008 at 5:54 PM, Scara Maccai <m_lists@yahoo.it> wrote:
> Since you always need the timestamp in your selects, have you tried indexing only the timestamp field?
> Your selects would be slower, but since client and sensor don't have that many distinct values compared to the number
ofrows you are inserting maybe the difference in selects would not be that huge. 

Even better might be partitioning on the timestamp.  IF all access is
in a certain timestamp range it's usually a big win, especially
because he can move to a new table every hour / day / week or whatever
and merge the old one into a big "old data" table.

pgsql-general by date:

Previous
From: Scara Maccai
Date:
Subject: Re: Using Postgres to store high volume streams of sensor readings
Next
From: "V S P"
Date:
Subject: [Q]updating multiple rows with Different values