BUG #16236: Invalid escape encoding

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: stephane(dot)campinas(at)gmail(dot)com
Subject: BUG #16236: Invalid escape encoding
Date: 2020-01-27 22:21:55
Message-ID: 16236-887912799bb3eb3c@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16236
Logged by: St├ęphane Campinas
Email address: stephane(dot)campinas(at)gmail(dot)com
PostgreSQL version: 12.1
Operating system: linux 5.4.14
Description:

Hi,

From the documentation [0] 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 [1] while mimicking the output of encode,
where you can get more details.

Cheers,

[0] https://www.postgresql.org/docs/12/functions-string.html
[1] https://github.com/crate/crate/pull/9540

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2020-01-27 22:34:58 Re: BUG #16235: ts_rank ignores match and only considers lower weighted vector
Previous Message Thomas Munro 2020-01-27 22:06:17 Re: BUG #16234: LDAP Query