| From: | Robert Creager <robert(at)logicalchaos(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-jdbc(at)lists(dot)postgresql(dot)org |
| Subject: | Re: COPY FROM STDIN hang |
| Date: | 2021-03-25 15:58:23 |
| Message-ID: | BE90E9D5-50C4-45A0-9DCF-8F44330A5F30@logicalchaos.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
> On Mar 23, 2021, at 3:51 PM, Robert Creager <robert(at)logicalchaos(dot)org> wrote:
>
>> 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?
>
Thanks Tom, since the reindex we’ve been unable to reproduce the problem again.
The big question is do you have any random thoughts on how a index may of gotten corrupted? The db lives on a two SSC ZFS mirror, so I’d not expect disk corruption.
Best,
Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prasanth | 2021-03-25 16:00:45 | Re: Exception while updating result set |
| Previous Message | Robert Creager | 2021-03-23 21:51:15 | Re: COPY FROM STDIN hang |