From: Reiner Dassing <dassing@wettzell.ifag.de>
To: pgsql-sql@postgresql.org
Subject: Best database structure for timely ordered values
Date: Mon, 18 Dec 2000 10:51:14 +0100
Message-ID: <3A3DDE12.AD1278D9@wettzell.ifag.de> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: dassing@wettzell.ifag.de
Subject: Re: Best database structure for timely ordered values
In-Reply-To: <3A3DDE12.AD1278D9@wettzell.ifag.de>
References: <3A3DDE12.AD1278D9@wettzell.ifag.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox