From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Peter Eisentraut <peter@eisentraut.org>
To: masano@sraoss.co.jp
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
Date: Wed, 07 Feb 2024 20:53:12 +0100
Message-ID: <d37f392a885435b8dc9e77d98c7191051d83da5c.camel@cybertec.at> (raw)
In-Reply-To: <f1fcbfd3-c12c-4aad-9f8e-fbaee3ef5658@eisentraut.org>
References: <18336-d3652b898b550423@postgresql.org>
<94d001ada27f1b39f00370a784395667aa6d44aa.camel@cybertec.at>
<f1fcbfd3-c12c-4aad-9f8e-fbaee3ef5658@eisentraut.org>
On Wed, 2024-02-07 at 08:49 +0100, Peter Eisentraut wrote:
> On 07.02.24 05:01, Laurenz Albe wrote:
> > On Wed, 2024-02-07 at 02:25 +0000, PG Bug reporting form wrote:
> > > In the PostgreSQL 16 release notes, there is an entry stating that the
> > > read-only server variables lc_collate and lc_ctype have been removed.
> > > However, the documentation for the SHOW command on the PostgreSQL official
> > > website (https://www.postgresql.org/docs/current/sql-show.html) still lists
> > > lc_collate and lc_ctype as valid variables.
> >
> > Right; here is a patch for that.
>
> I think the whole list of read-only options on the SHOW reference page
> is redundant and incomplete. A more complete list is at <sect1
> id="runtime-config-preset"> in config.sgml. This includes
> server_version and server_encoding, but not is_superuser. Maybe that's
> an omission? I think we should get rid of the list on the SHOW
> reference page.
That is much better; here is a patch.
Yours,
Laurenz Albe
Attachments:v2-0001-Doc-Remove-preset-parameters-from-SHOW-reference-.patch (text/x-patch, 2.8K) download
From f75d42e5df075c9e5b5bf6a8bfebaba4e66fca84 Mon Sep 17 00:00:00 2001
From: Laurenz Albe <laurenz.albe@cybertec.at>
Date: Wed, 7 Feb 2024 20:51:52 +0100
Subject: [PATCH v2] Doc: Remove preset parameters from SHOW reference page
The list of parameters is redundant and incomplete and constitutes
a backpatching hazard (it was missed by b0f6c43716), so let's get
rid of it.
Reported-by: Yuta Masano
Backpatch-to: 16
Discussion: https://postgr.es/m/18336-d3652b898b550423@postgresql.org
---
doc/src/sgml/ref/show.sgml | 60 ++------------------------------------
1 file changed, 2 insertions(+), 58 deletions(-)
diff --git a/doc/src/sgml/ref/show.sgml b/doc/src/sgml/ref/show.sgmlindex b3747b119f..3db13ad4cd 100644--- a/doc/src/sgml/ref/show.sgml+++ b/doc/src/sgml/ref/show.sgml@@ -52,64 +52,8 @@ SHOW ALL
<para>
The name of a run-time parameter. Available parameters are
documented in <xref linkend="runtime-config"/> and on the <xref
- linkend="sql-set"/> reference page. In- addition, there are a few parameters that can be shown but not- set:-- <variablelist>- <varlistentry>- <term><literal>SERVER_VERSION</literal></term>- <listitem>- <para>- Shows the server's version number.- </para>- </listitem>- </varlistentry>-- <varlistentry>- <term><literal>SERVER_ENCODING</literal></term>- <listitem>- <para>- Shows the server-side character set encoding. At present,- this parameter can be shown but not set, because the- encoding is determined at database creation time.- </para>- </listitem>- </varlistentry>-- <varlistentry>- <term><literal>LC_COLLATE</literal></term>- <listitem>- <para>- Shows the database's locale setting for collation (text- ordering). At present, this parameter can be shown but not- set, because the setting is determined at database creation- time.- </para>- </listitem>- </varlistentry>-- <varlistentry>- <term><literal>LC_CTYPE</literal></term>- <listitem>- <para>- Shows the database's locale setting for character- classification. At present, this parameter can be shown but- not set, because the setting is determined at database creation- time.- </para>- </listitem>- </varlistentry>-- <varlistentry>- <term><literal>IS_SUPERUSER</literal></term>- <listitem>- <para>- True if the current role has superuser privileges.- </para>- </listitem>- </varlistentry>- </variablelist></para>+ linkend="sql-set"/> reference page.+ </para>
</listitem>
</varlistentry>
--
2.43.0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: laurenz.albe@cybertec.at, peter@eisentraut.org, masano@sraoss.co.jp, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
In-Reply-To: <d37f392a885435b8dc9e77d98c7191051d83da5c.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox