Обсуждение: Re: [INTERFACES] Large objects, why not use the filesystem?

>> Right.  That would be a place where you couldn't use Matthew's
>> suggestion.  But in my case my 'client' is, ultimately, a cgi.
>> And now I'm wondering, why am I not using files?  I would hope
>> that postgres would be providing me with some kind of superior
>> performance than the file system.  Infact, I've always assumed
>> it.  But was I right to assume that?  Are there benchmarks out
>> there?
>
>No benchmarks are needed. Large objects are stored one per file,
>therefore you will see the same preformance.

Ok, I've seen all the xinv* files, I understand that.  But what
if the benefit of using large objects over files?  If there isn't
superior performance then why do it?

Gregory W Burnham
Software Engineer
Excite Labs
Faculty Of Education
Simon Fraser University
Vancouver, BC, V5A 1S6
604 291 3615 (ph)
604 291 5679 (fx)

> Ok, I've seen all the xinv* files, I understand that.  But what
> if the benefit of using large objects over files?  If there isn't
> superior performance then why do it?

To provide a consistant access interface in a client-server environment.
Managing one interface is usually easier than managing several (e.g.
postgres, html, ftp, ...) to support a single app.

I would expect the performance of LOs to be somewhat worse than direct
file system access to the same data, for a variety of reasons. But for
many applications that performance difference is not a critical issue.

                      - Tom