From cb62d0b3c372350b997733f41283cc35a6814024 Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Thu, 8 Sep 2022 09:56:50 +0200 Subject: [PATCH] doc: Fix PL/pgSQL casing to be consistent Ensure that all mentions of PL/pgSQL is cased equally, a few instances of PL/PgSQL had snuck in. Reviewed-by: Pavel Stehule Discussion: https://postgr.es/m/DDCF61C3-9E25-48A8-97BE-6113A93D54A5@yesql.se --- doc/src/sgml/plpgsql.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml index cf387dfc3f..d85f89bf30 100644 --- a/doc/src/sgml/plpgsql.sgml +++ b/doc/src/sgml/plpgsql.sgml @@ -5278,13 +5278,13 @@ a_output := a_output || $$ if v_$$ || referrer_keys.kind || $$ like '$$ strict_multi_assignment - Some PL/PgSQL commands allow assigning + Some PL/pgSQL commands allow assigning values to more than one variable at a time, such as SELECT INTO. Typically, the number of target variables and the number of source variables should match, though - PL/PgSQL will use NULL + PL/pgSQL will use NULL for missing values and extra variables are ignored. Enabling this - check will cause PL/PgSQL to throw a + check will cause PL/pgSQL to throw a WARNING or ERROR whenever the number of target variables and the number of source variables are different. @@ -5296,7 +5296,7 @@ a_output := a_output || $$ if v_$$ || referrer_keys.kind || $$ like '$$ too_many_rows - Enabling this check will cause PL/PgSQL to + Enabling this check will cause PL/pgSQL to check if a given query returns more than one row when an INTO clause is used. As an INTO statement will only ever use one row, having a query return multiple