From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | David North <dtn(at)corefiling(dot)co(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: bytea columns and large values |
Date: | 2011-09-28 15:18:27 |
Message-ID: | CAHyXU0zOvhC1GsQ+TLH3ve4AWkHkut+-qO8xP3zcjh3OLc-G8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Sep 28, 2011 at 3:28 AM, David North <dtn(at)corefiling(dot)co(dot)uk> wrote:
> On 28/09/11 01:50, Craig Ringer wrote:
>>
>> On 09/28/2011 01:01 AM, David North wrote:
>>
>>> testdb=# select * from problem_table;
>>> ERROR: invalid memory alloc request size 2003676411
>>
>> What Pg version are you using?
>>
>> On which platform?
>>
>> 32-bit or 64-bit OS? If 64-bit, with a 32-bit or 64-bit build of
>> PostgreSQL?
>
> psql (PostgreSQL) 9.0.4
>
> 64 bit fedora:
>
> Fedora release 14 (Laughlin)
> Linux mybox 2.6.35.14-95.fc14.x86_64 #1 SMP Tue Aug 16 21:01:58 UTC 2011
> x86_64 x86_64 x86_64 GNU/Linux
>
> I presume my build of PostgreSQL is x64 - ldd `which psql` spits out lots of
> references to lib64.
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.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2011-09-28 15:44:26 | What about improving the rules system we have, was Re: Rules going away |
Previous Message | Chris Travers | 2011-09-28 15:09:14 | Re: tubles matching |