Open davidbruce opened 2 years ago
I have attempted to work around https://github.com/Qovery/Replibyte/issues/208 by creating a manual dump file and then processing it with Replibyte. This unfortunately does not work and it just spins forever.
replibyte -c manual-local-config.yaml dump create --source_type postgresql --input --file manual-dumps/local_manual.dump
I stepped through the Replibyte code and found following code in dump.rs: 170 https://github.com/Qovery/Replibyte/blob/7458882e10a100373e837544aca3aa916d013fa1/replibyte/src/commands/dump.rs#L170-L181
Line 176 hangs forever when passing a .dump file or a .sql file. I assume this has something to do with the //FIXME 😅
.dump
.sql
//FIXME
Hi @davidbruce, thanks for reporting your issue and digging into it. Do you know the SQL line that makes your dump reading fail?
I have attempted to work around https://github.com/Qovery/Replibyte/issues/208 by creating a manual dump file and then processing it with Replibyte. This unfortunately does not work and it just spins forever.
I stepped through the Replibyte code and found following code in dump.rs: 170 https://github.com/Qovery/Replibyte/blob/7458882e10a100373e837544aca3aa916d013fa1/replibyte/src/commands/dump.rs#L170-L181
Line 176 hangs forever when passing a
.dump
file or a.sql
file. I assume this has something to do with the//FIXME
😅