Collected from the PG bugs email list.
|Reported by||Stéphane Campinas|
Body of first available message related to this bug follows.
The following bug has been logged on the website: Bug reference: 16236 Logged by: Stéphane Campinas Email address: (redacted) PostgreSQL version: 12.1 Operating system: linux 5.4.14 Description: Hi, From the documentation  about the encode function, the "escape" format should "convert zero bytes and high-bit-set bytes to octal sequences (\nnn) and doubles backslashes." However, executing "select encode(E'aaa\bccc', 'escape');" outputs "aaa\x08ccc", although according to the documentation I should get "aaa\010ccc". This was found in  while mimicking the output of encode, where you can get more details. Cheers,  https://www.postgresql.org/docs/12/functions-string.html  https://github.com/crate/crate/pull/9540
|2020-01-27 22:21:55+00||PG Bug reporting form||BUG #16236: Invalid escape encoding|
|2020-01-27 23:05:45+00||Tom Lane||Re: BUG #16236: Invalid escape encoding|
|2020-01-30 10:26:17+00||=?UTF-8?Q?St=C3=A9phane_Campinas?=||BUG #16236: Invalid escape encoding|
|2020-01-30 15:29:39+00||Tom Lane||Re: BUG #16236: Invalid escape encoding|