From: Tom Lane <tgl@sss.pgh.pa.us>
To: tomtrias@gmail.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Please make a note regarding the PL/pgSQL FOUND variable
In-reply-to: 
 <169894333941.1769272.13207972370571788231@wrigleys.postgresql.org>
References: 
 <169894333941.1769272.13207972370571788231@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Thu, 02 Nov 2023 16:42:19 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3475324.1699110971.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 04 Nov 2023 11:16:11 -0400
Message-ID: <3475325.1699110971@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3475325.1699110971%40sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> Since I was recently bitten by the fact that CREATE TABLE AS doesn't set=
 the
> PL/pgSQL variable FOUND, it would be nice if that were explicitly noted =
in
> the documentation.  Alternatively, if it COULD set the FOUND variable, t=
hat
> would be great, although I realize the difficulty of that when coupled w=
ith
> IF NOT EXISTS.

The documentation of FOUND is already quite explicit about which kinds
of statements set it:

https://www.postgresql.org/docs/current/plpgsql-statements.html#PLPGSQL-ST=
ATEMENTS-DIAGNOSTICS

I'm disinclined to put notes about PL/pgSQL features into command
reference pages that have nothing to do with PL/pgSQL.

			regards, tom lane