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

From Peter Geoghegan
Subject Re: Default gin operator class of jsonb failing with index row size maximum reached
Date
Msg-id CAM3SWZQxc51B0Nwfcde0Jmq2VWS8ZRNuJZ_mnsK__KQHQ7WyCQ@mail.gmail.com
Whole thread Raw
In response to Re: Default gin operator class of jsonb failing with index row size maximum reached  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Tue, Apr 8, 2014 at 4:07 PM, Michael Paquier
<michael.paquier@gmail.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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Default gin operator class of jsonb failing with index row size maximum reached
Next
From: "Prabakaran, Vaishnavi"
Date:
Subject: New option in pg_basebackup to exclude pg_log files during base backup