Re: bytea columns and large values

From: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
To: Alban Hertroys <haramrae(at)gmail(dot)com>
Cc: Radosław Smogura <rsmogura(at)softperience(dot)eu>, Merlin Moncure <mmoncure(at)gmail(dot)com>, David North <dtn(at)corefiling(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org
Subject: Re: bytea columns and large values
Date: 2011-09-29 12:48:12
Message-ID: CAKuK5J1Phdt40U_VdLxG8dQW5w_fPczZ8nF7WRr3Yx95ZttSqw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 29, 2011 at 7:30 AM, Alban Hertroys <haramrae(at)gmail(dot)com> wrote:
> On 29 September 2011 13:12, Radosław Smogura <rsmogura(at)softperience(dot)eu> wrote:
>>> sending ~1GB bytea values is borderline crazy, and is completely crazy
>>> if you are not absolutely sure the transmission is not 100% binary.  I
>>> don't know if the JDBC sends/receives bytea as binary, but it may not.
>>>  If not, you might have better luck with the large object interface.
>
>> "Crazy"? I thought that official stand was to keep such crazy values as
>> TOAST, and LOB interface isn't something worth of usage.

I'm not saying that placing such large values in a table (or LO) is a
good idea, but - if I had managed to put data *in* to a table that I
couldn't get back out, I'd be a bit cranky, especially if my attempt
to do so kills the backend I am using (which triggers a shutdown of
all other backends, no?).

--
Jon

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marti Raudsepp 2011-09-29 13:13:21 Re: Decimal vs. Bigint memory usage
Previous Message Alban Hertroys 2011-09-29 12:30:48 Re: bytea columns and large values