Re: Default gin operator class of jsonb failing with index row size maximum reached

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: obartunov(at)gmail(dot)com, Peter Geoghegan <pg(at)heroku(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Default gin operator class of jsonb failing with index row size maximum reached
Date: 2014-04-08 23:07:56
Message-ID: CAB7nPqT3Jg=3u8DPmqbbdf1=Dn2tykWm85vA1VoC1aPvekQarA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 9, 2014 at 6:48 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Oleg Bartunov <obartunov(at)gmail(dot)com> writes:
>> We are working to avoid this limitation.
>
> What do you mean by that ... do you see it as something that could be
> fixed quickly, or is this a long-term improvement project?
If this is a known limitation and no fix is planned for 9.4, could it
be possible to document it appropriately for this release? This would
surprise users.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-04-08 23:10:11 Re: Default gin operator class of jsonb failing with index row size maximum reached
Previous Message Stephen Frost 2014-04-08 22:51:04 Re: psql \d+ and oid display