Change CLIENT_ENCODING to client_encoding plus a question on "SET NAMES"

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: tanghy(dot)fnst(at)fujitsu(dot)com
Subject: Change CLIENT_ENCODING to client_encoding plus a question on "SET NAMES"
Date: 2021-06-23 05:16:29
Message-ID: 162442538953.701.18251359132909249828@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/13/multibyte.html
Description:

Here is a tiny modification at [1] (change CLIENT_ENCODING to lowercase):
-SET CLIENT_ENCODING TO 'value';
+SET client_encoding TO 'value';

Besides that, please allow me ask a question.
The PG doc at[1] said "you can use the standard SQL syntax SET NAMES for
this purpose", and it works. But no PG help-doc describes this SQL syntax of
"SET NAMES".
Is it on purpose or missed? I'd be grateful if anyone can share me the rule
on whether or not to add a SQL syntax in PG help-doc.

[1]https://www.postgresql.org/docs/13/multibyte.html

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2021-06-23 10:18:15 Incorrect Syntax in Function Syntax diagram
Previous Message David G. Johnston 2021-06-22 22:51:23 Re: Reverse btree indexes