On Jul 10, 2007, at 3:47 AM, Benoit Mathieu wrote:
I want to use postgres to store data and large files, typically
audio files from 100ko to 20Mo. For those files, I just need to
store et retrieve them, in an ACID way. (I don't need search, or
substring, or others functionnalities)
I saw pos
Hi all,
I want to use postgres to store data and large files, typically audio
files from 100ko to 20Mo. For those files, I just need to store et
retrieve them, in an ACID way. (I don't need search, or substring, or
others functionnalities)
I saw postgres offers at least 2 method : bytea column
On Tue, 10 Jul 2007, Alexander Staubo wrote:
> My take: Stick with TOAST unless you need fast random access. TOAST
> is faster, more consistently supported (eg., in Slony) and easier
> to work with.
Toasted bytea columns have some other disadvantages also:
1.
It is impossible to create its valu
On 7/10/07, Benoit Mathieu <[EMAIL PROTECTED]> wrote:
I saw postgres offers at least 2 method : bytea column with TOAST, or
large objects API.
From the documentation:
All large objects are placed in a single system table called pg_largeobject.
PostgreSQL also supports a storage system calle
Hi all,
I want to use postgres to store data and large files, typically audio
files from 100ko to 20Mo. For those files, I just need to store et
retrieve them, in an ACID way. (I don't need search, or substring, or
others functionnalities)
I saw postgres offers at least 2 method : bytea column
