Date: Mon, 30 Jan 2023 16:17:14 -0500
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: t.kitynski@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Suggestion for deprecated spellings
Message-ID: <Y9gz2rRpm6VKnC0M@momjian.us>
References: <167473556945.2667294.2003897901995802549@wrigleys.postgresql.org>
 <Y9grBFU+2DBXBB7z@momjian.us>
 <888259.1675112866@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <888259.1675112866@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/Y9gz2rRpm6VKnC0M%40momjian.us>
Precedence: bulk

On Mon, Jan 30, 2023 at 04:07:46PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > On Thu, Jan 26, 2023 at 12:19:29PM +0000, PG Doc comments form wrote:
> >> From time to time some spelling for given command gets obsolete, yet it is
> >> shown in the syntax on "equal rights" as other valid clauses.
> 
> > We don't need to show all _supported_ syntaxes in the "Synopsis"
> > section, so we could just remove them.
> 
> IIRC, there is precedent in COPY for moving obsolete alternatives
> to a separate part of the man page.  I'd prefer that to just
> removing them, because then there is no documentation to help
> someone understand what an old SQL script is doing.

Yeah, I remember that with COPY.  t.kitynski@gmail.com, please us that
as a guide.  Thanks.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

Embrace your flaws.  They make you human, rather than perfect,
which you will never be.