From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | Will Hartung <willhartung(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Loading table with indexed jsonb field is stalling |
Date: | 2019-05-21 00:54:27 |
Message-ID: | 792059f6-9815-03c2-5ccd-9d21c61925b6@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/20/19 7:21 PM, Will Hartung wrote:
>> On May 20, 2019, at 5:15 PM, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>>
>> 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.
> I don’t quite understand what you’re trying to achieve here. Is the intent essentially to access each individual element within the json on the select statement? There’s at least 50 elements in this thing,
Like I said earlier... "Are there a sufficiently small number of elements in
each traits object...?" But obviously there aren't.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Abhijit Gharami | 2019-05-21 08:57:45 | PITR based recovery in a primary/standby cluster setup |
Previous Message | Adrian Klaver | 2019-05-21 00:47:26 | Re: Loading table with indexed jsonb field is stalling |