pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
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 05:01:03 +0100
Message-ID: <94d001ada27f1b39f00370a784395667aa6d44aa.camel@cybertec.at> (raw)
In-Reply-To: <18336-d3652b898b550423@postgresql.org>
References: <18336-d3652b898b550423@postgresql.org>

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.

Yours,
Laurenz Albe

Attachments:

v1-0001-Remove-documentation-for-SHOW-LC_COLLATE-LC_CTYPE.patch (text/x-patch, 1.6K) download From 4205e98a9885e12fb15cf02ea619deeb31bc802a Mon Sep 17 00:00:00 2001 From: Laurenz Albe <laurenz.albe@cybertec.at> Date: Wed, 7 Feb 2024 04:55:51 +0100 Subject: [PATCH v1] Remove documentation for SHOW LC_COLLATE/LC_CTYPE These have been removed in b0f6c43716, but the documentation was not updated. Reported-by: Yuta Masano Backpatch-to: 16 Discussion: https://postgr.es/m/18336-d3652b898b550423@postgresql.org --- doc/src/sgml/ref/show.sgml | 24 ------------------------ 1 file changed, 24 deletions(-) diff --git a/doc/src/sgml/ref/show.sgml b/doc/src/sgml/ref/show.sgml index b3747b119f..5fbb5bbe01 100644 --- a/doc/src/sgml/ref/show.sgml +++ b/doc/src/sgml/ref/show.sgml @@ -77,30 +77,6 @@ SHOW ALL </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> -- 2.43.0

view thread (7+ messages)  latest in thread

Message-ID: <94d001ada27f1b39f00370a784395667aa6d44aa.camel@cybertec.at>
Permalink:  ../94d001ada27f1b39f00370a784395667aa6d44aa.camel@cybertec.at/
Also on:    postgresql.org/message-id/94d001ada27f1b39f00370a784395667aa6d44aa.camel@cybertec.at

 ·  · 

reply

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, masano@sraoss.co.jp, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command
  In-Reply-To: <94d001ada27f1b39f00370a784395667aa6d44aa.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