pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter@eisentraut.org>
To: 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, 7 Feb 2024 08:49:17 +0100
Message-ID: <f1fcbfd3-c12c-4aad-9f8e-fbaee3ef5658@eisentraut.org> (raw)
In-Reply-To: <94d001ada27f1b39f00370a784395667aa6d44aa.camel@cybertec.at>
References: <18336-d3652b898b550423@postgresql.org>
	<94d001ada27f1b39f00370a784395667aa6d44aa.camel@cybertec.at>

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.






view thread (7+ messages)  latest in thread

Message-ID: <f1fcbfd3-c12c-4aad-9f8e-fbaee3ef5658@eisentraut.org>
Permalink:  ../f1fcbfd3-c12c-4aad-9f8e-fbaee3ef5658@eisentraut.org/
Also on:    postgresql.org/message-id/f1fcbfd3-c12c-4aad-9f8e-fbaee3ef5658@eisentraut.org

 · 

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: peter@eisentraut.org, 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: <f1fcbfd3-c12c-4aad-9f8e-fbaee3ef5658@eisentraut.org>

* 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