Re: Loading table with indexed jsonb field is stalling
| От | Will Hartung |
|---|---|
| Тема | Re: Loading table with indexed jsonb field is stalling |
| Дата | |
| Msg-id | C3D03C39-1AFD-40BA-B4A4-4D6C483A1699@gmail.com обсуждение исходный текст |
| Ответ на | Re: Loading table with indexed jsonb field is stalling (Ron <ronljohnsonjr@gmail.com>) |
| Ответы |
Re: Loading table with indexed jsonb field is stalling
|
| Список | pgsql-general |
> On May 20, 2019, at 5:15 PM, Ron <ronljohnsonjr@gmail.com> wrote: > > Are there a sufficiently small number of elements in each traits object that you can do something like this, on the UNINDEXEDtable? > 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 elementwithin the json on the select statement? There’s at least 50 elements in this thing, and the structure is not flat,nor is it static and consistent. Similar, sure. Perfectly congruent, no.
В списке pgsql-general по дате отправления: