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
Date: Mon, 20 May 2019 14:12:56 -0400
Message-ID: <24634.1558375976@sss.pgh.pa.us> (raw)
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, willhartung@gmail.com, pgsql-general@lists.postgresql.org
Subject: Re: Loading table with indexed jsonb field is stalling
In-Reply-To: <24634.1558375976@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox