From: | Will Hartung <willhartung(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Will Hartung <willhartung(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Loading table with indexed jsonb field is stalling |
Date: | 2019-05-20 18:17:47 |
Message-ID: | 36F908DB-2F04-44F8-8C2E-7FD630882E0E@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On May 20, 2019, at 11:12 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Hmm, so not a deadlock (plus you're running a version that has that
> bug fixed). It sounds like you might have hit an actual bug, perhaps
> one that causes it to endlessly re-split an index page, or something
> along that line. But it's going to be hard to find the cause without
> a test case. I don't suppose you can anonymize your data to the
> point where you'd have a publishable test case?
That would take some time, thankfully it seems reproducible with a few million rows.
I’ve moved the files around a little bit (not aggressively) and it still stalled, so I don’t think it’s something specific to the data. But we’ll have to play with it and see.
Thanks.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-05-20 18:18:02 | Re: INSERT where not exists with foreign key |
Previous Message | Will Hartung | 2019-05-20 18:15:59 | Re: Loading table with indexed jsonb field is stalling |