From: Tom Lane <tgl@sss.pgh.pa.us>
To: Will Hartung <willhartung@gmail.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: Loading table with indexed jsonb field is stalling
In-reply-to: <90835D2B-1FBA-4F26-8157-7C831C24B266@gmail.com>
References: 
 <CAKMEDdxE95SC76wadMzrH454HpvCV4tOdEmuZRO=pwArEw6YVg@mail.gmail.com>
 <20505.1558202555@sss.pgh.pa.us>
 <90835D2B-1FBA-4F26-8157-7C831C24B266@gmail.com>
Comments: In-reply-to Will Hartung <willhartung@gmail.com>
	message dated "Mon, 20 May 2019 11:05:35 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <24633.1558375976.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Mon, 20 May 2019 14:12:56 -0400
Message-ID: <24634.1558375976@sss.pgh.pa.us>
Precedence: bulk

Will Hartung <willhartung@gmail.com> writes:
>> On May 18, 2019, at 11:02 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> In addition to the questions about what PG version you're using, is
>> the backend process that's doing the load actually consuming CPU time,
>> or is it just sitting?

> It’s consuming both CPU and disk space.

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?

			regards, tom lane