Best database structure for timely ordered values - Mailing list pgsql-sql

From Reiner Dassing
Subject Best database structure for timely ordered values
Date
Msg-id 3A3DDE12.AD1278D9@wettzell.ifag.de
Whole thread Raw
Responses Re: Best database structure for timely ordered values
List pgsql-sql
Hi!

I am thinking about the best structure of a database to describe timely ordered
values.
The timely ordered values are the results of different sensors measuring
environmental
parameters like temperatur, pressure, humidity.

The database has to define the kind of measurements, kind of sensors, place of
them,
ie., more or less static information.
The main part will be the measurement values ordered by the time or epoch due to
UTC.
The primary index must be the epoch.
As there will be no deletion from this data I fear - due to the internal
representation
of B-trees - the performance will degrade very soon. The expected number of
measurements
will easily reach some millions.

Any comments or ideas?
Reiner


pgsql-sql by date:

Previous
From: "Trewern, Ben"
Date:
Subject: RE: readline ??
Next
From: Frank Joerdens
Date:
Subject: Re: Subqueries in Non-SELECT Queries