Message-ID: <3f27cc04de0b6d1d8df0a22a2811dd99b823d1e9.camel@cybertec.at>
Subject: Re: Unclear Wording
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Bruce Momjian <bruce@momjian.us>, pg@kirasoft.com,
	pgsql-docs@lists.postgresql.org
Date: Wed, 08 Jun 2022 04:34:37 +0200
In-Reply-To: <Yp/qFiNg6VapoZeZ@momjian.us>
References: 
	<165455351426.573551.7050474465030525109@wrigleys.postgresql.org>
	 <Yp/qFiNg6VapoZeZ@momjian.us>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/3f27cc04de0b6d1d8df0a22a2811dd99b823d1e9.camel%40cybertec.at>
Precedence: bulk

On Tue, 2022-06-07 at 20:15 -0400, Bruce Momjian wrote:
> > Page: https://www.postgresql.org/docs/14/plpgsql-errors-and-messages.html
> > Description:
> > 
> > Dear Sirs,
> >    From the page on RAISE ...
> >    I read this 3 times and tripped over "write a format", which should be use
> > (or specify) a format string ...
> > 
> > Current:
> > After level if any, you can write a format (which must be a simple string
> > literal, not an expression). The format string specifies the error message
> > text to be reported. 
> > 
> > Suggested Rewrite:
> > After level if any, you can specify a format string (which must be a simple
> > string literal, not an expression). The format string specifies the error
> > message text to be reported. 
> 
> Good idea, patch attached.

+1

Yours,
Laurenz Albe