On 7/15/22 13:35, Andres Freund wrote: >> (And do we want to fix it now, regardless?) > > Yes.
Cool. I can get on board with that. >> What guarantees are we supposed to be making for log encoding? > > I don't know, but I don't think not caring at all is a good > option. Particularly for unauthenticated data I'd say that escaping everything > but printable ascii chars is a sensible approach. It'll also be painful for anyone whose infrastructure isn't in a Latin character set... Maybe that's worth the tradeoff for a v1. Is there an acceptable approach that could centralize it, so we fix it once and are done? E.g. a log_encoding GUC and either conversion or escaping in send_message_to_server_log()? --Jacob
