Dear Melih,
>> I think we should add description to doc that it is more likely happen to fail
>> the initial copy user should enable binary format after synchronization if
>> tables have original datatype.
>
> I tried to explain when binary copy can cause failures in the doc. What exactly
> do you think is missing?
I assumed here that "copy_format" and "binary" were combined into one option.
Currently the binary option has descriptions :
```
Even when this option is enabled, only data types having binary send and receive functions will be transferred in
binary
```
But this is not suitable for initial data sync, as we knew. I meant to say that
it must be updated if options are combined.
Note that following is not necessary for PG16, just an improvement for newer version.
Is it possible to automatically switch the binary option from 'true' to 'false'
when data transfer fails? As we found that while synchronizing the initial data
with binary format may lead another error, and it can be solved if the options
is changed. When DBAs check a log after synchronization and find the output like
"binary option was changed and worker will restart..." or something, they can turn
"binary" on again.
Best Regards,
Hayato Kuroda
FUJITSU LIMITED