handle audiofiles in postgres

edisan wrote:

Can anyone used or tell me how to handle audio files in postgres

Audio files may be in wav / vox / dss format and each have average 30
min running time.

probably too large to want to store in the database, as a 30 minute PCM
.WAV file in CD quality could easily be 300 megabytes, even in a MP3
format it might be 30MB if high-fidelity, and maybe 6MB if lower voice
quality, thats -still- larger than I'd want to store as database rows,
anyways, there's nothing really relational about the audio data.

I'd suggest storing them as standard disk files, and putting the
location (path, filename) in the database. if you need to access them
from multiple systems, store them on an http or similar server....

-----Original Message-----
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org]On Behalf Of edisan
Sent: Thursday, 3 September 2009 2:48 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] handle audiofiles in postgres

Can anyone used or tell me how to handle audio files in postgres

Audio files may be in wav / vox / dss format and each have average 30 min running time.

Thanks in advance

Regards
edi

I store several hundred as blobs.
http://www.postgresql.org/docs/current/static/largeobjects.html

Allan

The material contained in this email may be confidential, privileged or copyrighted. If you are not the intended recipient, use, disclosure or copying of this information is prohibited. If you have received this document in error, please advise the sender and delete the document. Neither OneSteel nor the sender accept responsibility for any viruses contained in this email or any attachments.

urs.edisan@gmail.com (edisan) writes:

Can anyone used or tell me how to handle audio files in postgres

Audio files may be in  wav / vox / dss format and each have average 30 min
running time.

In principle, you could store these as "BLOB" data; I'd quite prefer
storing this as "bytea" data.

The TOAST capability
<http://www.postgresql.org/docs/8.4/interactive/storage-toast.html&gt;
means that these "BLOBs" are actually stored in side tables, which
should be good for efficiency in that they won't make data tuples
enormous even though there's enormous data tied to them.

As a result, queries on metadata (e.g. - the other attributes of the
data) can be nicely efficient despite the bulky data.

It's not obvious, however, that storing the files in the database is
preferable to:

- Putting the files in a filesystem, perhaps with cryptic names
(hashes?)

- Storing the metadata about the files in the database, referencing the
files' names

If there's good reason to store the files in the DBMS, then do so; just
make sure there's good reason for it!
--
let name="cbbrowne" and tld="ca.afilias.info" in name ^ "@" ^ tld;;
Christopher Browne
"Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"