Re: Large Objects

>>
> Intresting.
> What is the size when bytea become inafective ?
>
> Currently i keep all my products images in bytea record. is it
> practical ?

Well I am going to make the assumption that you product images are small...
sub 100k or something. Bytea is just fine for that. The problem is when
the binary you want to store is 50 megs. When you access that file you
will be using 50 megs of ram to do so.

Large Objects don't work that way, you don't have the memory overhead. So
it really depends on what you want to store.

>
> how slower is it then accessing an image on a file system ( like ext3 ) ?

Well that would be an interesting test. Ext3 is very slow. I would assume
that Ext3 would be faster just because of the database overhead. However
you gain from having the images in the database for flexibility and
manageability.

Sincerely,

Joshua D. Drake

>
>
> Cheers
>
>>
>> pg_largeobject is more efficient than BYTEA for larger binaries.
>>
>> Sincerely,
>>
>> Joshua D. Drake
>>
>>
>

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL