Re: COPY FROM STDIN hang

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Creager <robert(at)logicalchaos(dot)org>
Cc: pgsql-jdbc(at)lists(dot)postgresql(dot)org
Subject: Re: COPY FROM STDIN hang
Date: 2021-03-23 21:38:01
Message-ID: 1012455.1616535481@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Robert Creager <robert(at)logicalchaos(dot)org> writes:
> On Mar 23, 2021, at 3:16 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> You mean the backend hangs? Can you get a stack trace from that?

> The entire backend doesn’t hang, we’re able to process queries on other connections. It’s just the COPY FROM thread that’s hung.

Hmm, that set of traces doesn't really look like it's hung,
it might just be taking a long time.

A different theory, which is hard to prove without debug symbols
to provide more detail in the trace, is that it might be looping
due to following a closed loop of btree page right-links. Which
shouldn't happen normally, but perhaps this index is corrupt.
Can you try reindexing the indexes of the COPY's target table?

regards, tom lane

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Robert Creager 2021-03-23 21:51:15 Re: COPY FROM STDIN hang
Previous Message Robert Creager 2021-03-23 21:30:37 Re: COPY FROM STDIN hang