Re: Default gin operator class of jsonb failing with index row size maximum reached - Mailing list pgsql-hackers

From Oleg Bartunov
Subject Re: Default gin operator class of jsonb failing with index row size maximum reached
Date
Msg-id CAF4Au4yiGmNHnHbQ9Ax54yAZxzPbMOEQVS+fiCMKzbGJzGbZ=g@mail.gmail.com
Whole thread Raw
In response to Re: Default gin operator class of jsonb failing with index row size maximum reached  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Apr 9, 2014 at 1:48 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Oleg Bartunov <obartunov@gmail.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?

Unfortunately, It's long-term project VODKA, we hope to use spgist
(also needed some adjustment) for keys+values instead of btree.
Hopefully, we'll show something at PGCon.

>
>                         regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)
Next
From: Andrew Dunstan
Date:
Subject: Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation)