Re: BUG #15083: [54000] ERROR: total size of jsonb array elements exceeds the maximum of 268435455 bytes

From: Vinston Pandiyan <vinston(dot)pandiyan(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15083: [54000] ERROR: total size of jsonb array elements exceeds the maximum of 268435455 bytes
Date: 2018-02-23 19:34:21
Message-ID: CACs8k4a_bz17buZX5v5HwyunuB6A32N0uNje3WnLHCbEMeKgOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

if you can suggest any workaround this? or it is possible to compress the
data and store?

On Fri, Feb 23, 2018 at 1:48 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Fri, Feb 23, 2018 at 11:45 AM, Vinston Pandiyan <
> vinston(dot)pandiyan(at)gmail(dot)com> wrote:
>
>> Is there way to fix this? i want to keep 500k rows in json or jsonb field?
>> please help me with this, it is possible to do it in postgres?
>>
>
> ​For the typical user, no, there is no way to get rid of the limitation -
> you will need to decide how you want to go about avoiding it.
>
> David J.
>
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-02-23 20:12:31 Re: BUG #15082: PostgreSQL 11 dev bug with window range partition by QUERY
Previous Message David G. Johnston 2018-02-23 19:27:29 Re: maximum for auto_explain.log_min_duration doesn't seem to make sense