Re: more than 2GB data string save

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Steve Atkins <steve(at)blighty(dot)com>
Cc: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: more than 2GB data string save
Date: 2010-02-10 06:36:37
Message-ID: dcc563d11002092236r45840889lae2385cf9798bbf8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Feb 9, 2010 at 11:26 PM, Steve Atkins <steve(at)blighty(dot)com> wrote:
>
> On Feb 9, 2010, at 9:52 PM, Scott Marlowe wrote:
>
>> On Tue, Feb 9, 2010 at 9:38 PM, AI Rumman <rummandba(at)gmail(dot)com> wrote:
>>> How to save 2 GB or more text string in Postgresql?
>>> Which data type should I use?
>>
>> If you have to you can use either the lo interface, or you can use
>> bytea.  Large Object (i.e. lo) allows for access much like fopen /
>> fseek  etc in C, but the actual data are not stored in a row with
>> other data, but alone in the lo space.  Bytea is a legit type that you
>> can have as one of many in a row, but you retrieve the whole thing at
>> once when you get the row.
>
> Bytea definitely won't handle more than 1 GB. I don't think the lo interface
> will handle more than 2GB.

That really depends on how compressible it is, doesn't it?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message AI Rumman 2010-02-10 06:38:03 Re: more than 2GB data string save
Previous Message Steve Atkins 2010-02-10 06:26:45 Re: more than 2GB data string save