From: | Steve Atkins <steve(at)blighty(dot)com> |
---|---|
To: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: more than 2GB data string save |
Date: | 2010-02-10 06:26:45 |
Message-ID: | A381E230-272F-432B-A2FB-FAAD3DBD8D07@blighty.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
>
> Preferred way to store 2GB data is to put it into a file and put the
> name of the file into the database.
This.
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2010-02-10 06:36:37 | Re: more than 2GB data string save |
Previous Message | Scott Marlowe | 2010-02-10 05:52:31 | Re: more than 2GB data string save |