We've managed to reproduce client <-> server de-synchronization triggered by this, which we are seeing in production.
Libpq considers '< 2TDCEZ' a sufficient response to '> BDESS', when according to specification one more 'Z' is expected.
A bit more context and a MRE: https://github.com/itrofimow/libpq_protocol_desync