Q: disabling codecs while transferring data?

I have a couple of potentially silly questions.

Suppose I am reading rows in batches from a table in a source database and writing the same rows in batches into another table in another database.

1. Can I disable all decoders on the connection to the source database as well as all encoders on the connection to the destination database and just deal with records that have a binary representation of each column?
2. Can I do so on a statement by statement basis such that for all the statements that are not directly involved into this data triangulation the codecs still apply? Or should I have a separate connection for all the meta operations like introspecting the current status and checkpointing progress?

Thank you!

No files, tests, or entry points are named in the issue. Start by tracing asyncpg's codec behavior for source and destination connections and for individual statements. Done means establishing whether binary-only transfer and statement-level codec control are supported, or documenting the required connection strategy.

Written by the indexing model from the issue text.