Re: long transfer time for binary data

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: long transfer time for binary data
Date: 2016-01-23 22:38:49
Message-ID: 56A400F9.2020305@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/23/2016 2:19 PM, Johannes wrote:
> I save my images as large object, which afaik is in practise not
> readable with a binary cursor (we should use the lo_* functions). And of
> course I already use the LargeObjectManager of the postgresql jdbc library.

afaik, Large Objects are completely independent of the other mode
stuff. they are stored and transmitted in binary.

I haven't read this whole ongoing thread, just glanced at messages as
they passed by over the past week or whatever, but I have to say, I
would NOT be storing 11MB images directly in SQL, rather, I would store
it on a file server, and access it with nfs or https or whatever is most
appropriate for the nature of the application. I would store the
location and metadata in SQL.

--
john r pierce, recycling bits in santa cruz

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2016-01-23 22:41:22 A motion
Previous Message Johannes 2016-01-23 22:19:13 Re: long transfer time for binary data