Re: issue with lo_lseek - it returns 4

[Konstantin Izmailov <kizmailov@xxxxxxxxx>]

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@xxxxxxxxxxxxx> wrote:

Konstantin Izmailov <pgfizm@xxxxxxxxx> 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