Replibyte: issues while dumping using replibyte (SIGKILL - force quit)

Questions and Answers
1

Hey there,
I am trying to dump all the tables from a schema present in my DB

Here is the command:
replibyte -c config/replibyte.yaml dump create

⠁ [00:06:18] [########################################################################################################>—] 1.80GiB/1.86GiB (12s)

Here is the result that I am getting
Job 1, ‘replibyte -c config/replibyte.y…’ terminated by signal SIGKILL (Forced quit)

I tried a couple of times, and its stopping at 1.8Go
Is there some kindof limit that can be reached / how shall I proceed? Should I create mutliple dump an reconcile?
Do you have any idea :slight_smile:

I tried as well the sampling but it didn’t work, it was crashing
[00:01:37] [----------------------------------------------------------------------------------------------------------------] 0B/100.00MiB (0s)
thread ‘main’ panicked at ‘called Option::unwrap() on a None value’, /root/src/subset/src/postgres.rs:152:87

2

Hello @Rimbaud_Van_Eetvelde,

I am not aware of any kind of limitations on that front :frowning:
Could you maybe raise the issue directly on the replibyte repo if not done already?

Thanks !

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.