Re: Error creating gin index on jsonb columns - Mailing list pgsql-hackers
Currently, after hitting the error, the indexes were still created but marked with status of "invalid"
Looks like we shall see inserts to fail with the index on the column, regardless of the index status ("valid" or "invalid"), if we start to receive the "bad" values? Maybe I shall drop all these indexes.
If it's a bug, what information would be needed to trigger a bug fix? Is there a formal channel?
Thanks.
-glenn
On Fri, Oct 16, 2015 at 6:43 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Glenn Zhu <gzhu@medallia.com> writes:
> We are currently running 9.4.4. 9.4.5 notes have two references to gin
> index but does not seem to address the issue.
> We are however able to create same index on some other databases. So it
> maybe data related or size of table related?
I'd guess that it's triggered by a specific data item or set of data
items. Doubt it has anything to do with table size per se. The quoted
value is 0x78000000, which makes me think that something is
misinterpreting a plain C string as a varlena value (with a length word),
or something along that line.
regards, tom lane
Glenn Zhu
SaaS Operations | ❖ Medallia, Inc.
pgsql-hackers by date: