In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

Currently, generic documentation exists for how to create/configure custom datatype converters, with recently added specific sections in the MySQL and Oracle connector docs. However, this documentation does not mention that to allow the value to pass through to the converter when connecting to Postgres (both with the `pgoutput` and `pgproto` plugins), one needs to set `include.unknown.datatypes` to `true`, otherwise the value is nullified and never sent.

Implementation ideas (optional)

Add a section, similar in nature to the ones in the MySQL and Oracle pages, that documents the slight behavior difference when using custom connectors in Postgres.