From: | Benoit Mathieu <benoit(dot)mathieu(at)mist-technologies(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | TOAST, large objects and ACIDity |
Date: | 2007-07-10 12:34:37 |
Message-ID: | 46937CDD.9080308@mist-technologies.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 with TOAST, or
large objects API.
I wonder what are the differences of the 2 methods.
* I found that large objects need a vacuum after delete to really
release place. That may be handled by a trigger or automatic vaccum, is
it right ?
* Large objects are used via a special API available in libpq C client
library.
* I really care keeping my transaction fully ACID. Documentation on
large objects doesn't explicitly say if lo_import an lo_export (and
other primitives) are fully ACID. Some ideas ?
* I going to bench insertion and read with this 2 methods.
other advices are wellcome, particularly about integration of TOAST or
large objects with pgclusters.
thanks
Benoit
From | Date | Subject | |
---|---|---|---|
Next Message | Reid Thompson | 2007-07-10 12:38:28 | Re: free scheduled import utility |
Previous Message | alexander lunyov | 2007-07-10 12:34:30 | Re: russian case-insensitive regexp search not working |