| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pelletier(dot)michel(at)gmail(dot)com |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Minor result error in binary strings documentation |
| Date: | 2020-05-31 01:02:14 |
| Message-ID: | 15129.1590886934@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
PG Doc comments form <noreply(at)postgresql(dot)org> writes:
> On the page:
> https://www.postgresql.org/docs/12/functions-binarystring.html
> The result for decode('123\000456', 'escape') is incorrect, it should be:
> # select decode('123\000456', 'escape');
> decode
> ------------------
> \x31323300343536
The example is "correct" as given, because it assumes bytea_output is set
to escape, as noted at the top of the page. For v13, I have adjusted all
the examples on this page to follow the modern default of bytea_output =
hex, but I don't plan to retrofit the older branches that way.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josef Šimánek | 2020-06-01 22:40:09 | Re: Another modest proposal for docs formatting: catalog descriptions |
| Previous Message | PG Doc comments form | 2020-05-30 17:17:45 | Minor result error in binary strings documentation |