timescaledb-parallel-copy icon indicating copy to clipboard operation
timescaledb-parallel-copy copied to clipboard

FATAL error

Open jayadevanm opened this issue 4 years ago • 1 comments

I am testing this on Alpine Linux, with PostgreSQL 12.5, TimescaleDB 2.0.1. With a batch size of 1000000, it worked fine. When I increased the batch size to 10000000, I started getting and error. FATAL: terminating connection because protocol synchronization was lost Google led me to this https://github.com/lib/pq/issues/473#issue-163349398 Not sure if that is the same. The file has 133 million records and PostgreSQL's COPY works without any issues. I am trying to optimize the batch-size/number-of-workers combinations and see if I can get a better throughput with parallel-copy. So far, I have been able to get roughly 90,000-1,00,000 per second with default COPY while parallel-copy gave me 50,000-60,000 per second.

jayadevanm avatar Feb 04 '21 04:02 jayadevanm

@jayadevanm With #63 merged, the utility no longer uses lib/pq under the hood. Can you rebuild with the most recent commit and see if this solves your issue?

jchampio avatar Jun 17 '22 16:06 jchampio