| From: | Oleg Bartunov <obartunov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(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 22:09:24 |
| Message-ID: | CAF4Au4yiGmNHnHbQ9Ax54yAZxzPbMOEQVS+fiCMKzbGJzGbZ=g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 9, 2014 at 1: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?
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-04-08 22:18:31 | Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) |
| Previous Message | Peter Geoghegan | 2014-04-08 21:57:44 | Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) |