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

Can timescaledb-parrallel-copy read files still being written to or resume where it got up to #55

Open
anthonysomerset opened this issue Feb 16, 2022 · 1 comment

Comments

@anthonysomerset
Copy link

we are migrating a fairly large set of zabbix data from one server to another (about 1TB) migrating the data is no issue but our bottleneck appears to be specifically the dump of data from the source server to a csv rather than the write out.

can this tool read CSV files that are still being written to and what happens when it gets to the end?

can the tool also do some kind of resume function where it starts where it left off?

@MetalBlueberry
Copy link
Contributor

I would say you can tail | timescaledb-parallel-copy and it will keep reading until you terminate the program. I recommend you to give it a try.

about resuming on where it was left... I would say no. The tool simply reads a file and puts it into the database. It doesn't handle cases such as partial copy or resuming after a failure.
Said that, the tool does report the number of successfully copied rows, so you may be able to resume manually with that information.

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