| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | ROS Didier <didier(dot)ros(at)edf(dot)fr>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: JSONB maximal length ? |
| Date: | 2019-10-07 21:39:08 |
| Message-ID: | CAHOFxGoec_y7CnCSmn=L0G1fApe+0eoLo7b0YG67cZt+05S9kQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> Hi
>>
>> By inserting data in a JSONB type column I got the following error
>> message:
>>
>> *>> *
>>
>> *ERROR: string too long to represent as jsonb string*
>>
>> *DETAIL: Due to an implementation restriction, jsonb strings cannot
>> exceed 268435455 bytes.*
>>
>> *<< *
>>
>> could anyone confirm that there is a size limit for JSONB type fields ?
>>
>>
Have you looked at bytea datatype? I believe this would allow up to 1GB
which is the max file size so the maximum (minus some overhead) for a row.
Perhaps though, storing files of unusually large size should be done
outside of the database.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2019-10-07 23:17:47 | Re: Declarative Range Partitioning Postgres 11 |
| Previous Message | Michael Lewis | 2019-10-07 21:27:07 | Re: Performance on JSONB select |