From: | "Nathan Buchanan" <nbinont(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | storage of sensor data with Fourier transforms |
Date: | 2007-05-05 05:13:23 |
Message-ID: | d51c18ed0705042213n773b927t11f1d8bedb6f07d2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello!
I have a potential situation where I will have a lot of sensor data coming
in very often. (every second or so) The sensor data is from physics type
measurements, and will normally follow a slowly changing pattern with
sinusoidal disturbances. The overall shape of the data is more important
than catching high frequency disturbances.
I had the idea of taking the Fourier transform of the waveform and storing
the waveform internally that way to reduce storage requirements. When I get
some free cycles, I may try doing this. I would want it to be done in the
database in such a way that the user can still join to a table using this
internal storage scheme.
Why am I mailing this list? I'd like to ask if anyone has heard of someone
doing anything like this. I did a small search of the lists and internet but
didn't come up with anything. I just don't want to re-invent the wheel.
Thanks for your time,
Nathan
--
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Got Mole problems? Call Avogadro at 6.02 x 10^23.
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2007-05-05 05:45:39 | Re: storage of sensor data with Fourier transforms |
Previous Message | Bruce Momjian | 2007-05-05 03:45:44 | Re: pgsql: Teach tuplesort.c about "top N" sorting, in which only the first |