Re: issue with lo_lseek - it returns 4 - Mailing list pgsql-general

From Konstantin Izmailov
Subject Re: issue with lo_lseek - it returns 4
Date
Msg-id 1225592b0906171730k75fa9eb6t1ef74c8a93b0294f@mail.gmail.com
Whole thread Raw
In response to Re: issue with lo_lseek - it returns 4  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
It would be great to remove the limitation. I can image various possibilities if Postgres can handle larger lo objects. For example, to stream HD content from DB to a multimedia device for displaying.

Would that be technically hard to do? My impression is that lo has pretty scalable implementation already.

On Wed, Jun 17, 2009 at 4:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Konstantin Izmailov <pgfizm@gmail.com> writes:
> Out of curiosity, what if lo object has size > 4GB, how lo_tell return its
> size? Looks like this is an interface issue.

That's simple: it can't have such a size.

Allowing LOs bigger than 2GB is on the TODO list, but don't hold your
breath.  Most people who are interested in objects that large are
storing them out in the filesystem anyway.

                       regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Some strange bug with drop table with slony cluster
Next
From: Sam Wun
Date:
Subject: Too many postgres instances