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

From Scara Maccai
Subject Re: Using Postgres to store high volume streams of sensor readings
Date
Msg-id 260691.6571.qm@web28105.mail.ukl.yahoo.com
Whole thread Raw
In response to Re: Using Postgres to store high volume streams of sensor readings  ("Ciprian Dorin Craciun" <ciprian.craciun@gmail.com>)
Responses Re: Using Postgres to store high volume streams of sensor readings  ("Scott Marlowe" <scott.marlowe@gmail.com>)
List pgsql-general
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. 






pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: delete commands fails silently to delete primary key
Next
From: "Scott Marlowe"
Date:
Subject: Re: Using Postgres to store high volume streams of sensor readings