From: Tom Lane <tgl@sss.pgh.pa.us>
To: rsindlin@gmail.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: bytea documentation error
In-reply-to: 
 <167907221210.1803488.5939223864945604536@wrigleys.postgresql.org>
References: <167907221210.1803488.5939223864945604536@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Fri, 17 Mar 2023 16:56:52 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <558533.1679169901.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 18 Mar 2023 16:05:01 -0400
Message-ID: <558534.1679169901@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/558534.1679169901%40sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> I believe there is a documentation error in the example for "8.4.1 bytea=
 Hex
> Format"
> (https://www.postgresql.org/docs/current/datatype-binary.html#id-1.5.7.1=
2.9).
> The example is
> `SELECT '\xDEADBEEF';`
> However, when I try that on my system [psql (13.9 (Ubuntu
> 13.9-1.pgdg20.04+1), server 13.10 (Ubuntu 13.10-1.pgdg20.04+1))], it wor=
ks
> *but* the result is type `text` per `pg_typeof()`.  I believe the exampl=
e
> needs to be corrected with an explicit cast to `bytea`.

Yeah, that's not really right.  Also, this example is pretty shoddy
compared to the one for escape format a little further down.
Will fix, thanks for the report!

			regards, tom lane