From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Loading table with indexed jsonb field is stalling |
Date: | 2019-05-21 00:15:16 |
Message-ID: | 0a8876b8-f4de-4bc2-72c8-afe5dfe6fde2@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/20/19 6:51 PM, Will Hartung wrote:
>> On May 20, 2019, at 4:27 PM, Ron <ronljohnsonjr(at)gmail(dot)com
>> <mailto:ronljohnsonjr(at)gmail(dot)com>> wrote:
>>
>> I'm confused. You wrote above that loading without indexes and with just
>> the PK works just fine; if you *really* need it loaded in Aurora or
>> production, just drop the indexes beforehand?
>
> Because the jsonb_path_ops index does not rebuild, and it’s the heart of
> that table.
>
> The table is essentially worthless without that index to us.
Clarified.
Are there a sufficiently small number of elements in each traits object that
you can do something like this, on the UNINDEXED table?
SELECT traits->element1, traits->element2, count(*)
from eis_entry
group by traits->element1, traits->element2;
Sure it would run for a long time, but might show you where the problem lies.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Will Hartung | 2019-05-21 00:21:09 | Re: Loading table with indexed jsonb field is stalling |
Previous Message | Adrian Klaver | 2019-05-21 00:14:01 | Re: Loading table with indexed jsonb field is stalling |