Best database structure for timely ordered values

From: Reiner Dassing <dassing(at)wettzell(dot)ifag(dot)de>
To: pgsql-sql(at)postgresql(dot)org
Subject: Best database structure for timely ordered values
Date: 2000-12-18 09:51:14
Message-ID: 3A3DDE12.AD1278D9@wettzell.ifag.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Frank Joerdens 2000-12-18 10:43:21 Re: Subqueries in Non-SELECT Queries
Previous Message Trewern, Ben 2000-12-18 09:32:45 RE: readline ??