Jelte Fennema bb5c494104 Enable binary encoding by default on PG14 ... Since PG14 we can now use binary encoding for arrays and composite types that contain user defined types. This was fixed in this commit in Postgres: 670c0a1d47 This change starts using that knowledge, by not necessarily falling back to text encoding anymore for those types. While doing this and testing a bit more I found various cases where binary encoding would fail that our checks didn't cover. This fixes those cases and adds tests for those. It also fixes EXPLAIN ANALYZE never using binary encoding, which was a leftover of workaround that was not necessary anymore. Finally, it changes the default for both `citus.enable_binary_protocol` and `citus.binary_worker_copy_format` to `true` for PG14 and up. In our cloud offering `binary_worker_copy_format` already was true by default. `enable_binary_protocol` had some bug with MX and user defined types, this bug was fixed by the above mentioned fixes.		2021-09-06 10:27:29 +02:00
..
backend	Enable binary encoding by default on PG14	2021-09-06 10:27:29 +02:00
include	Apply latest version compat without conflicts	2021-09-03 16:09:59 +03:00
test	Enable binary encoding by default on PG14	2021-09-06 10:27:29 +02:00