Re: Error creating gin index on jsonb columns - Mailing list pgsql-hackers
Hi Tom,
Thanks for the reply.
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? So far, the failed cases reported are from large tables, with number of rows between 150 to 350 millions.
What would you need in terms of test cases?
Thank you very much.
-glenn
On Fri, Oct 16, 2015 at 6:28 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Glenn Zhu <gzhu@medallia.com> writes:
> We are getting an error on the following statement:
> CREATE INDEX CONCURRENTLY customer_jsonb_fields_idx ON customer USING gin
> (jsonb_fields jsonb_path_ops);
> ERROR: invalid memory alloc request size 2013265920
> Anyone know what is causing it?
Sounds like a bug from here. What PG version is this exactly? If it's
not the latest minor releases, try updating. If it's still there, see if
you can extract a test case that you can share.
regards, tom lane
Glenn Zhu
SaaS Operations | ❖ Medallia, Inc.
pgsql-hackers by date: