From: Tom Lane <tgl@sss.pgh.pa.us>
To: Reiner Dassing <dassing@wettzell.ifag.de>
Cc: pgsql-sql@postgresql.org
Subject: Re: Best database structure for timely ordered values
Date: Mon, 18 Dec 2000 09:56:55 -0500
Message-ID: <18883.977151415@sss.pgh.pa.us> (raw)
In-Reply-To: <3A3DDE12.AD1278D9@wettzell.ifag.de>
References: <3A3DDE12.AD1278D9@wettzell.ifag.de>
Reiner Dassing <dassing@wettzell.ifag.de> writes:
> 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.
Nonsense. btree should work just fine for that. Use a timestamp
column for the primary key, and away you go.
(Actually, time alone doesn't seem like it'd be necessarily unique,
so maybe you don't want to call it a primary key. But certainly
you can make a non-unique index on that column.)
regards, tom lane
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: tgl@sss.pgh.pa.us, dassing@wettzell.ifag.de
Subject: Re: Best database structure for timely ordered values
In-Reply-To: <18883.977151415@sss.pgh.pa.us>
References: <3A3DDE12.AD1278D9@wettzell.ifag.de> <18883.977151415@sss.pgh.pa.us>
* 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