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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, obartunov(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 23:10:11
Message-ID: CAM3SWZQxc51B0Nwfcde0Jmq2VWS8ZRNuJZ_mnsK__KQHQ7WyCQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 8, 2014 at 4:07 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> 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.

It looks like the default GIN opclass will be changed, so it becomes a
matter of opting in to the particular set of trade-offs that the
current default represents. Presumably that includes the size
limitation, which isn't separately documented at present.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Prabakaran, Vaishnavi 2014-04-09 00:06:30 New option in pg_basebackup to exclude pg_log files during base backup
Previous Message Michael Paquier 2014-04-08 23:07:56 Re: Default gin operator class of jsonb failing with index row size maximum reached