Re: Loading table with indexed jsonb field is stalling
От | Ron |
---|---|
Тема | Re: Loading table with indexed jsonb field is stalling |
Дата | |
Msg-id | 0a8876b8-f4de-4bc2-72c8-afe5dfe6fde2@gmail.com обсуждение исходный текст |
Ответ на | Re: Loading table with indexed jsonb field is stalling (Will Hartung <willhartung@gmail.com>) |
Ответы |
Re: Loading table with indexed jsonb field is stalling
|
Список | pgsql-general |
On 5/20/19 6:51 PM, Will Hartung wrote:
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.
On May 20, 2019, at 4:27 PM, Ron <ronljohnsonjr@gmail.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.
Angular momentum makes the world go 'round.
В списке pgsql-general по дате отправления: