Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FATAL error #47

Open
jayadevanm opened this issue Feb 4, 2021 · 1 comment
Open

FATAL error #47

jayadevanm opened this issue Feb 4, 2021 · 1 comment

Comments

@jayadevanm
Copy link

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 lib/pq#473 (comment)
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.

@jchampio
Copy link
Contributor

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants