Re: Storing images in PostgreSQL databases (again)

From: "Marco Bizzarri" <marco(dot)bizzarri(at)gmail(dot)com>
To: tijod(at)yahoo(dot)fr
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Storing images in PostgreSQL databases (again)
Date: 2006-10-05 08:22:46
Message-ID: 3f0d61c40610050122i47f1dfffh1154f872da024119@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi.

I can provide some "insight" on the difference between the two interfaces.

AFAIK, the difference is in size of the file you can store, and in the
interface you have when you want to access.

The size is not important (I think), since you are far below the limit.

For the interface, the bytea gives you a "query" based interfaces,
while largeobject are able to provide a file based interface.

With Large Object, you can avoid reading the whole object with one
read, or you can even move inside the Large Object, which can be
useful if you have large files stored.

I think there are differences also in how the space is reclaimed, but
my PostgreSQL - Fu stops here.

Regards
Marco

--
Marco Bizzarri
http://notenotturne.blogspot.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Bauer 2006-10-05 08:48:56 Re: Major Performance decrease after some hours
Previous Message Matthias.Pitzl 2006-10-05 07:34:58 Re: Help required